Is Ingrid down?

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.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being deployed

A fix has been implemented and we are monitoring the results.

The incident has been resolved, all of failed shipments were rebooked successfully.

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.

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.

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.

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.

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

We are currently looking into an issue with booking of Budbee shipments where no label or tracking numbers are returned in some instances. We have reached out to Budbee about this and are working together to find a resolution.

Budbee has identified the issue and a fix for this is about to be deployed to their production environment.

Budbee reports that the issue is resolved. Feedback internally also confirms this.

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.

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

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.