Ingrid Outage History

Ingrid is up right now

There were 9 Ingrid outages since February 10, 2026 totaling 63h 50m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://ingrid.statuspage.io

Minor April 27, 2026

TA: Postnord API is reporting unresponsiveness

Detected by Pingoru
Apr 27, 2026, 06:15 AM UTC
Resolved
Apr 27, 2026, 06:40 AM UTC
Duration
24m
Affected: Transport Administration
Timeline · 3 updates
  1. identified Apr 27, 2026, 06:15 AM UTC

    We have identified and been made aware of booking issue with Postnord where the Postnord API times out in the booking request. This is being looked in to and escalated to Postnord.

  2. monitoring Apr 27, 2026, 06:34 AM UTC

    Postnord reports that they have mitigated the issue and we are monitoring our logs. Initial inspection can confirm that the error message has dissappeared.

  3. resolved Apr 27, 2026, 06:40 AM UTC

    Postnord confirms the issue on their end due to functionality deployment. Logged timeframe of issues with connectivity to their API. from 08:03:50 to 08:31:34. No issues identified on Ingrid's end.

Read the full incident report →

Major April 15, 2026

Returns end users not getting their label

Detected by Pingoru
Apr 15, 2026, 08:04 AM UTC
Resolved
Apr 15, 2026, 11:49 AM UTC
Duration
3h 44m
Affected: Returns
Timeline · 3 updates
  1. investigating Apr 15, 2026, 08:04 AM UTC

    We are currently investigating this issue.

  2. identified Apr 15, 2026, 08:45 AM UTC

    Issue identified, mitigated and in progress of re-processing affected Returns.

  3. resolved Apr 15, 2026, 11:49 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 18, 2026

DPD Meta API booking issues to Belgium.

Detected by Pingoru
Mar 18, 2026, 07:34 AM UTC
Resolved
Mar 19, 2026, 01:14 PM UTC
Duration
1d 5h
Affected: Transport Administration
Timeline · 2 updates
  1. identified Mar 18, 2026, 07:34 AM UTC

    DPD Reports to us that they are experiencing issues with their META API that affects bookings to some postal codes in Belgium (BE). They are working on a fix and will let us know as soon as this is fixed. This issue can create error messages when booking with certain DPD Products to Belgium specifically and is not related to Ingrid's platform.

  2. resolved Mar 19, 2026, 01:14 PM UTC

    No additional feedback received from DPD. Closing this informational incident.

Read the full incident report →

Critical March 4, 2026

Domain Issues

Detected by Pingoru
Mar 04, 2026, 09:39 AM UTC
Resolved
Mar 04, 2026, 02:07 PM UTC
Duration
4h 27m
Affected: Ingrid Merchant Platform
Timeline · 5 updates
  1. investigating Mar 04, 2026, 09:39 AM UTC

    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.

  2. identified Mar 04, 2026, 09:47 AM UTC

    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

  3. monitoring Mar 04, 2026, 10:26 AM UTC

    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).

  4. resolved Mar 04, 2026, 02:07 PM UTC

    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.

  5. postmortem Mar 10, 2026, 12:42 PM UTC

    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

Read the full incident report →

Minor February 26, 2026

Budbee Tracking events synchronisation

Detected by Pingoru
Feb 26, 2026, 11:28 AM UTC
Resolved
Feb 26, 2026, 02:36 PM UTC
Duration
3h 7m
Affected: Tracking
Timeline · 3 updates
  1. investigating Feb 26, 2026, 11:28 AM UTC

    We are currently investigating the issue of budbee tracking events not being synchronised properly for a part of our merchants.

  2. monitoring Feb 26, 2026, 12:34 PM UTC

    A fix has been implemented, we are currently observing the results.

  3. resolved Feb 26, 2026, 02:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 25, 2026

Bring PUP API Issue

Detected by Pingoru
Feb 25, 2026, 08:44 AM UTC
Resolved
Feb 25, 2026, 10:27 AM UTC
Duration
1h 43m
Affected: Transport Administration
Timeline · 2 updates
  1. monitoring Feb 25, 2026, 08:44 AM UTC

    Bring has contacted us about an incident they have created due to an issue in their system regarding "PUP API is receiving incorrect data from the backend system" Please read more here for status: https://status.bring.systems/incidents/29810gdjbzp4 Contact Bring for further questions.

  2. resolved Feb 25, 2026, 10:27 AM UTC

    Bring reports that the issue is resolved. More information here: https://status.bring.systems/incidents/29810gdjbzp4

Read the full incident report →

Minor February 12, 2026

Problem to scan label barcode for Posti

Detected by Pingoru
Feb 12, 2026, 09:41 AM UTC
Resolved
Feb 12, 2026, 12:45 PM UTC
Duration
3h 3m
Affected: Transport Administration
Timeline · 3 updates
  1. identified Feb 12, 2026, 09:41 AM UTC

    We have been made aware of a recent change that was introduced on Posti labels that make it hard or impossible to scan the tracking number barcode. We are working on adjusting this to produce fully usable labels for Posti again.

  2. monitoring Feb 12, 2026, 10:16 AM UTC

    A fix has been implemented and released to our production environment. We are currently observing if it fixed the issue, all failed shipments need to be rebooked to have a valid label.

  3. resolved Feb 12, 2026, 12:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 10, 2026

Earlybird: Shipment bookings are denied/failing

Detected by Pingoru
Feb 10, 2026, 02:25 PM UTC
Resolved
Feb 11, 2026, 06:14 AM UTC
Duration
15h 48m
Affected: Transport Administration
Timeline · 2 updates
  1. identified Feb 10, 2026, 02:25 PM UTC

    We have received this information from Early Bird regarding an issue in their systems. Please note that Ingrid is not the source of this issue. Communication from Early Bird: -------------------------- We are sorry to inform you that we are experiencing an issue currently which leads to many denied bookings. We are very sorry for the inconvenience. We will provide an update as soon as we have more information. Kind regards, Technical Support & Integrations Early Bird --------------------------

  2. resolved Feb 11, 2026, 06:14 AM UTC

    Closing this since no further feedback has been received from Earlybird.

Read the full incident report →

Major February 10, 2026

Intermittent issues with domain names for turnr.se

Detected by Pingoru
Feb 10, 2026, 12:49 PM UTC
Resolved
Feb 10, 2026, 02:40 PM UTC
Duration
1h 51m
Affected: Returns
Timeline · 3 updates
  1. identified Feb 10, 2026, 12:49 PM UTC

    We are currently experiencing intermittent issues with connectivity to the old/legacy turnr.se domain names. Investigations are running. For information, these legacy domain names should not be used and should be replaced as soon as possible. Please update your integrations for future proofing with these endpoints instead of turnr.se api.turnr.se -> api.ingrid.com/returns backoffice.turnr.se -> returns-portal.ingrid.com returns.turnr.se -> returns.ingrid.com

  2. identified Feb 10, 2026, 02:01 PM UTC

    We have identified some integrations on our end that uses the old domain name, this affects non critical features like order updates that are pushed to us. We will re-fetch the information we might have missed as well so there should be no impact for our customers other than some delays in updated information.

  3. resolved Feb 10, 2026, 02:40 PM UTC

    The Domain name issue is now resolved and solution is being propagated within the DNS network. Any issues should be resolved once that update propagates

Read the full incident report →

Looking to track Ingrid downtime and outages?

Pingoru polls Ingrid's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Ingrid reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Ingrid alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Ingrid for free

5 free monitors · No credit card required