Is Ingrid down?
Last checked 6m agoNo incidents right now.
Ingrid is operational right now. Last checked 6m ago; the most recent incident resolved 10d ago.
Real-time Ingrid status, recent outages, and incident history — pulled directly from Ingrid's official status page at https://ingrid.statuspage.io every 5 minutes. Pingoru tracks 6 Ingrid services and has captured 10 incidents in the last 90 days (98.15% uptime). Get email, Slack, Discord, or webhook alerts the moment Ingrid reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Transport Administration
Timeline · 2 updates
- monitoring · Jun 24, 2026, 09:07 AM UTC
We have been made aware of an outage for the carrier DAO. The issue is reported to be resolved on their end but further disruptions may occur during the day. Please see information below from carrier, comments by Ingrid added within brackets [] for clarity. ------------------ Our [DAO's] ISP had an outage this night/early morning. It has caused some internal disruptions in our [DAO's] service. We are working on resolving the issue with high priority. As of now, the API is up again and the database server is responding. There might be some further interruptions today, while we [DAO] finetune the network connectivity issues. -------------------
- resolved · Jun 24, 2026, 09:46 AM UTC
Closing this since DAO has communicated this as resolved. Please contact carrier for further information if necessary.
Latest: Closing this since DAO has communicated this as resolved. Please contact carrier for further information if necessary.
-
- CheckoutTransport Administration
Timeline · 5 updates
- investigating · Jun 16, 2026, 11:21 AM UTC
We have recently identified an error in the system that affects transport administration where booking is currently not possible. 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.
- investigating · Jun 16, 2026, 11:23 AM UTC
We are continuing to investigate this issue.
- identified · Jun 16, 2026, 11:33 AM UTC
Prio: Critical Scope: TA and Checkout Update: We have noticed an issue with connectivity to one of our services, a fix has been proposed
- resolved · Jun 16, 2026, 11:38 AM UTC
The incident has now been resolved. We will be sending a follow up email, containing a post mortem of the incident, within the next week.
- postmortem · Jun 25, 2026, 12:17 PM UTC
On Tuesday, 16 June 2026, Ingrid experienced a disruption to its booking service. The issue was caused by a configuration error that made the booking service unavailable for affected merchants. The disruption lasted approximately 36 minutes. The issue was identified and resolved during the same afternoon. Service was restored by reverting the configuration change, and merchant reports confirmed full recovery by ~13:30 CEST. Affected bookings could be retried and completed after service was restored. **Timeline \(CEST\)** * ~12:53 — Booking failures begin * ~13:05 — Issue detected; investigation initiated * ~13:15 — Incident published on status page * ~13:28 — Fix applied * ~13:30 — Recovery confirmed
Latest: On Tuesday, 16 June 2026, Ingrid experienced a disruption to its booking service. The issue was caused by a configuration error that made the booking service unavailable for affect…
-
- Transport AdministrationAPI Connectivity
Timeline · 2 updates
- monitoring · May 29, 2026, 11:08 AM UTC
All the postnord shipments might face difficulties in either booking or printing the labels. Unfortunately there's nothing we can do from our side, awaiting postnord to fix the issue.
- resolved · May 29, 2026, 02:04 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Returns
Timeline · 4 updates
- investigating · May 26, 2026, 08:20 AM UTC
We are currently investigating this issue.
- identified · May 26, 2026, 08:29 AM UTC
The issue has been identified and a fix is being deployed
- monitoring · May 26, 2026, 08:44 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved · May 26, 2026, 09:20 AM UTC
The incident has been resolved, all of failed shipments were rebooked successfully.
Latest: The incident has been resolved, all of failed shipments were rebooked successfully.
-
- Transport Administration
Timeline · 5 updates
- investigating · May 20, 2026, 06:24 AM UTC
We have recently identified an error in the system that affects bulk shipment bookings that result in timeouts. 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.
- identified · May 20, 2026, 09:18 AM UTC
Prio: High Scope: Bulk Shipments Update: The issue has been partially resolved as we have addressed the root cause of the timeout issues, we are still investigating remaining complications with the bulk shipment workflows that are causing them to not function as expected and will update as we get further details on what is causing those issues.
- monitoring · May 20, 2026, 11:37 AM UTC
The error appears to have been resolved. We are currently monitoring the fix and we will update here as we confirm the resolution of this incident.
- resolved · May 20, 2026, 12:07 PM UTC
The incident has now been resolved. We will be sending a follow up email, containing a post mortem of the incident, within the next week.
- postmortem · May 28, 2026, 09:31 AM UTC
On Wednesday, 20 May 2026, Ingrid experienced a service disruption affecting bulk and consolidated shipment booking flows within the Transport product. Some merchants received timeout errors \(HTTP 504\) when attempting to create bulk or consolidated shipments. Standard \(non-bulk\) shipment flows were largely unaffected. The issue was caused by two separate internal issues: a request timeout setting that did not accommodate longer-running booking flows, and a regression in retry handling within an internal booking service. Both were identified and corrected during the same day, and resolution was verified the same afternoon. ### Timeline \(CEST\) * **20 May, 08:16** — Incident declared * **20 May, ~09:10** — Partial mitigation applied \(gateway timeouts increased\) * **20 May, ~10:54** — Fix applied \(retry/loop regression corrected\) * **20 May, ~13:45** — Resolution verified
Latest: On Wednesday, 20 May 2026, Ingrid experienced a service disruption affecting bulk and consolidated shipment booking flows within the Transport product. Some merchants received time…
-
See the full Ingrid outage history
1 more incident in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Ingrid outage history →Or sign up free to get alerts when Ingrid breaks · 10 free monitors · No credit card
- Carrier DAO outages reported ResolvedStarted Jun 24, 2026, 09:07 AM UTC · Resolved Jun 24, 2026, 09:46 AM UTC · 38m
- Booking unavailable ResolvedStarted Jun 16, 2026, 11:21 AM UTC · Resolved Jun 16, 2026, 11:38 AM UTC · 17m
- Postnord API Timeout ResolvedStarted May 29, 2026, 11:08 AM UTC · Resolved May 29, 2026, 02:04 PM UTC · 2h 56m
- Started May 26, 2026, 08:20 AM UTC · Resolved May 26, 2026, 09:20 AM UTC · 59m
- Bulk Shipment Timeouts ResolvedStarted May 20, 2026, 06:24 AM UTC · Resolved May 20, 2026, 12:07 PM UTC · 5h 42m
- Transport booking issues with Budbee ResolvedStarted May 11, 2026, 07:18 AM UTC · Resolved May 11, 2026, 12:02 PM UTC · 4h 44m