Domain Issues

Incident Report for Ingrid

Postmortem

On Wednesday, March 4, 2026, Ingrid experienced a service disruption affecting access to Ingrid services and APIs. The issue was caused by a domain-related DNS failure.

The issue was identified and corrected during the same morning. Recovery began immediately after the fix was implemented. Due to normal DNS caching behavior across networks and providers, some customers may have experienced residual access issues for a limited period afterward.

Timeline (CET)

10:31 — We began receiving reports of service availability issues
10:37 — Incident response initiated
10:40 — Root cause identified
10:48 — Fix implemented
11:14 — Recovery confirmed

Posted Mar 10, 2026 - 14:36 CET

Resolved

The incident has now mainly been resolved. We are reminding any user that if you still see connectivity issues, please flush local DNS cache or use a public resolver temporarily (1.1.1.1 / 8.8.8.8).

We will be sending a follow up email,
containing a post mortem of the incident, within the next week.

Posted Mar 04, 2026 - 15:07 CET

Monitoring

The DNS incident affecting ingrid.com / api.ingrid.com has been resolved at source. Some providers may still serve cached DNS for a limited time. If you still see connectivity issues, please flush local DNS cache or use a public resolver temporarily (1.1.1.1 / 8.8.8.8).

Posted Mar 04, 2026 - 11:26 CET

Identified

Prio: Critical
Scope: All Ingrid Sites
Update: The issue has been identified to be with our domain provider. We are currently are reaching out to get this resolved as soon as possible

Posted Mar 04, 2026 - 10:47 CET

Investigating

We have recently identified an error in the system that affects the Ingrid domain.
We are currently investigating this with the highest priority and we will be
updating you with the status of the investigation and resolution of
this issue through this channel. We apologize for the inconvenience in the
meantime and ask for your continued patience as we work on
resolving this matter.

Posted Mar 04, 2026 - 10:39 CET

This incident affected: Ingrid Merchant Platform.