Ingrid incident

Returns end users not getting their label

Major Resolved View vendor source →

Ingrid experienced a major incident on April 15, 2026 affecting Returns, lasting 3h 44m. The incident has been resolved; the full update timeline is below.

Started
Apr 15, 2026, 08:04 AM UTC
Resolved
Apr 15, 2026, 11:49 AM UTC
Duration
3h 44m
Detected by Pingoru
Apr 15, 2026, 08:04 AM UTC

Affected components

Returns

Update timeline

  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.

  4. postmortem Jun 09, 2026, 11:56 AM UTC

    On Sunday, 25 May 2026, Ingrid Returns experienced a disruption affecting return shipment booking and return label generation, beginning at approximately 14:13 CEST. The issue was caused by a limit condition being exceeded within Ingrid's return shipment creation pipeline, causing booking requests to fail. The issue was identified on the morning of 26 May following merchant reports. A fix was deployed by approximately 10:30 CEST, restoring the ability to book new return shipments. Previously failed bookings were reprocessed and confirmed cleared by approximately 11:17 CEST. We acknowledge the detection gap and are implementing alerting to catch this type of failure earlier. ### Timeline \(CEST\) * **25 May, ~14:13** — Returns booking failures begin * **26 May, ~09:30** — Incident identified and declared following merchant reports * **26 May, ~10:30** — Fix deployed; new return bookings restored * **26 May, ~11:17** — Backlog of failed shipments confirmed fully reprocessed * **26 May, ~11:20** — Incident resolved