- Detected by Pingoru
- May 11, 2026, 07:18 AM UTC
- Resolved
- May 11, 2026, 12:02 PM UTC
- Duration
- 4h 44m
Affected: Transport Administration
Timeline · 3 updates
-
identified May 11, 2026, 07:18 AM UTC
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.
-
monitoring May 11, 2026, 11:00 AM UTC
Budbee has identified the issue and a fix for this is about to be deployed to their production environment.
-
resolved May 11, 2026, 12:02 PM UTC
Budbee reports that the issue is resolved. Feedback internally also confirms this.
Read the full incident report →
- 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
-
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.
-
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.
-
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 →
- 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
-
investigating Apr 15, 2026, 08:04 AM UTC
We are currently investigating this issue.
-
identified Apr 15, 2026, 08:45 AM UTC
Issue identified, mitigated and in progress of re-processing affected Returns.
-
resolved Apr 15, 2026, 11:49 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
resolved Mar 19, 2026, 01:14 PM UTC
No additional feedback received from DPD. Closing this informational incident.
Read the full incident report →
- 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
-
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.
-
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
-
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).
-
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.
-
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 →
- 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
-
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.
-
monitoring Feb 26, 2026, 12:34 PM UTC
A fix has been implemented, we are currently observing the results.
-
resolved Feb 26, 2026, 02:36 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
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 →
- 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
-
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.
-
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.
-
resolved Feb 12, 2026, 12:45 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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 --------------------------
-
resolved Feb 11, 2026, 06:14 AM UTC
Closing this since no further feedback has been received from Earlybird.
Read the full incident report →
- 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
-
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
-
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.
-
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 →
Critical January 26, 2026 - Detected by Pingoru
- Jan 26, 2026, 07:51 AM UTC
- Resolved
- Jan 30, 2026, 10:15 AM UTC
- Duration
- 4d 2h
Affected: CheckoutTransport AdministrationAPI Connectivity
Timeline · 5 updates
Read the full incident report →
Critical November 14, 2025 - Detected by Pingoru
- Nov 14, 2025, 02:05 PM UTC
- Resolved
- Nov 14, 2025, 02:46 PM UTC
- Duration
- 41m
Affected: Returns
Timeline · 4 updates
-
investigating Nov 14, 2025, 02:05 PM UTC
We have recently identified an error in the Returns Portal system that affects the entire platform. 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.
-
monitoring Nov 14, 2025, 02:15 PM UTC
The error appears to have been resolved. We are currently monitoring the system and we will update here as we confirm the resolution of this incident.
-
resolved Nov 14, 2025, 02:46 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 Nov 14, 2025, 03:18 PM UTC
Todays outage was caused by a configuration change to our infrastructure related to the Returns backend, in preparation of black week that should have been an instant change. This however cause unintended changes wich resulted in the downtime. we're investigating why the change was not instant. The actual downtime was between 14:58 and 15:15.
Read the full incident report →
- Detected by Pingoru
- Oct 09, 2025, 08:24 AM UTC
- Resolved
- Oct 09, 2025, 09:56 AM UTC
- Duration
- 1h 31m
Affected: Returns
Timeline · 3 updates
-
investigating Oct 09, 2025, 08:24 AM UTC
We are currently experiencing issues with the customer facing returns portal, which is intermittently timing out and thus causing random service disruptions. We are investigating the issue.
-
monitoring Oct 09, 2025, 08:58 AM UTC
The error appears to have been resolved. We are currently monitoring the service and we will update here as we confirm the resolution of this incident.
-
resolved Oct 09, 2025, 09:56 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.
Read the full incident report →
- Detected by Pingoru
- Sep 23, 2025, 09:32 AM UTC
- Resolved
- Sep 23, 2025, 01:00 PM UTC
- Duration
- 3h 27m
Affected: Transport Administration
Timeline · 4 updates
-
investigating Sep 23, 2025, 09:32 AM UTC
We are aware of an error that comes from the Post Nord API when attempting to book shipments "API Acess Denied" Multiple of our customers are affected and it appeared at the same time. We have contacted Postnord for troubleshooting and we will provide updates once available.
-
identified Sep 23, 2025, 10:52 AM UTC
Post Nord is continuing to work on the issue. Further details might be provided on the Post Nord Status page here: https://apistatus-public-postnord.statuspage.io/incidents/fczkwrd0r6sj
-
monitoring Sep 23, 2025, 11:44 AM UTC
Post Nord reports that they have resolved the issue on their end. But any of our customers that still experience issues need to contact their Post Nord representative for some kind of update per customer. We are looking to if there is something else we can provide to Post Nord to fully resolve this faster.
-
resolved Sep 23, 2025, 01:00 PM UTC
Post Nord has, as mentioned already communicated, marked this issue as resolved. From what we can see in our logs, the errors has been reduced or removed. We also have confirmation from our customers that bookings works as intended. Post Nord API endpoint(s) had issues between approximate 11:00 CET through approximate 13:10 CET according to our logs.
Read the full incident report →
- Detected by Pingoru
- Sep 22, 2025, 07:49 AM UTC
- Resolved
- Sep 22, 2025, 08:17 AM UTC
- Duration
- 27m
Affected: Transport Administration
Timeline · 5 updates
-
investigating Sep 22, 2025, 07:49 AM UTC
We are currently aware of and investigating a communication issue within our internal subsystems. This does not affect all carriers or shipping methods. But when booking shipments, this error can appear "transport: Error while dialing: dial tcp: lookup service-sites-cache on xx.xx.xx.xx: no such host" We are looking into a remediation for this issue.
-
identified Sep 22, 2025, 07:57 AM UTC
Issue has been identified and fix is on it's way. Further updates will be provided when available.
-
identified Sep 22, 2025, 08:03 AM UTC
We are continuing to work on a fix for this issue.
-
monitoring Sep 22, 2025, 08:05 AM UTC
Unfortunately a default message was sent out a minute ago instead of this message. The connection to our subsystems has now been restored since a couple of minutes back and are looking good. We are continuing to monitor this.
-
resolved Sep 22, 2025, 08:17 AM UTC
This incident is now resolved and no further errors appear when conducting bookings for certain carriers. The issue occurred due to a subsystem communication failure within our platform. The communication issue appeared intermittently between 08:58 and 09:55.
Read the full incident report →
- Detected by Pingoru
- Sep 12, 2025, 05:49 AM UTC
- Resolved
- Sep 12, 2025, 06:54 AM UTC
- Duration
- 1h 5m
Affected: API Connectivity
Timeline · 2 updates
-
identified Sep 12, 2025, 05:49 AM UTC
Prio: High Scope: Bring Services Update: Bring API services are currently down. We have contacted the carrier for updates on the status and timeline for the fix
-
resolved Sep 12, 2025, 06:54 AM UTC
Bring has gotten back to us. The API was down "Due to an issue in MS, but now all the APIs are up again."
Read the full incident report →
- Detected by Pingoru
- Aug 18, 2025, 09:32 AM UTC
- Resolved
- Aug 18, 2025, 09:57 AM UTC
- Duration
- 25m
Affected: Transport Administration
Timeline · 3 updates
-
investigating Aug 18, 2025, 09:32 AM UTC
We are currently monitoring a communication issue with connection to the EarlyBird API. This shows itself as intermittent timeouts when attempting to book shipments with EarlyBird. EarlyBird has confirmed this and are working on stabilizing their API endpoints.
-
monitoring Aug 18, 2025, 09:51 AM UTC
No additional connectivity issues detected for the last 20 minutes. We are continuing to monitor the situation.
-
resolved Aug 18, 2025, 09:57 AM UTC
EarlyBird reports that as of 11:40 there are no further issues reported and everything works as expected.
Read the full incident report →
- Detected by Pingoru
- Aug 18, 2025, 09:31 AM UTC
- Resolved
- Aug 18, 2025, 10:12 AM UTC
- Duration
- 41m
Affected: Transport Administration
Timeline · 3 updates
-
monitoring Aug 18, 2025, 09:31 AM UTC
We are currently monitoring a communication issue with connection to the Helthjem API. This shows itself as intermittent timeouts when attempting to book shipments with Helthjem. Helthjem has confirmed this and are working on stabilizing their API endpoints.
-
monitoring Aug 18, 2025, 09:51 AM UTC
No additional connectivity issues detected for the last 20 minutes. We are continuing to monitor the situation.
-
resolved Aug 18, 2025, 10:12 AM UTC
Helthjem reports that the intermittent issues are resolved since around 12:00
Read the full incident report →
- Detected by Pingoru
- Jul 06, 2025, 07:48 AM UTC
- Resolved
- Jul 06, 2025, 09:03 AM UTC
- Duration
- 1h 14m
Affected: Transport Administration
Timeline · 3 updates
-
identified Jul 06, 2025, 07:48 AM UTC
There is currently an issue identified in DHL API which causes bookings through our platform to fail. DHL is working on the issue. More information here: https://status.api.dhl.com/
-
identified Jul 06, 2025, 08:34 AM UTC
DHL is reporting that they are working on the issue. We will update here as well until resolved. For more information, see: https://status.api.dhl.com/
-
resolved Jul 06, 2025, 09:03 AM UTC
DHL reports their incident to be resolved. Confirmed from our end as well. Please see https://status.api.dhl.com/ for incident details.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2025, 07:14 PM UTC
- Resolved
- Jun 12, 2025, 08:01 PM UTC
- Duration
- 46m
Affected: CheckoutTrackingTransport AdministrationReturnsAPI ConnectivityIngrid Merchant Platform
Timeline · 5 updates
-
identified Jun 12, 2025, 07:14 PM UTC
We are currently experiencing issues due to out hosting provider Google has global outades of their Compute platform.
-
identified Jun 12, 2025, 07:14 PM UTC
We are continuing to work on a fix for this issue.
-
identified Jun 12, 2025, 07:16 PM UTC
For reference: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW
-
monitoring Jun 12, 2025, 07:40 PM UTC
Google reports that the issues has been mitigated across their regions where we operate. We are monitoring the situation. https://status.cloud.google.com/
-
resolved Jun 12, 2025, 08:01 PM UTC
Operations appear to be back to normal with the Google platform for our regions. We are continuing to monitor the situation.
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2025, 12:30 PM UTC
- Resolved
- Jun 11, 2025, 01:30 PM UTC
- Duration
- 1h
Affected: Transport Administration
Timeline · 3 updates
-
identified Jun 11, 2025, 01:18 PM UTC
We have identified an issue with our integration with Instabox that produces issues when attempting to book shipments. The issue has been identified and mitigation is underway.
-
monitoring Jun 11, 2025, 01:37 PM UTC
The issue has been resolved and we are currently monitoring our systems for potential additional issues.
-
resolved Jun 11, 2025, 01:48 PM UTC
No additional issues reported after fix was deployed. Issue classified as resolved.
Read the full incident report →
- Detected by Pingoru
- May 20, 2025, 11:45 AM UTC
- Resolved
- May 20, 2025, 01:30 PM UTC
- Duration
- 1h 44m
Affected: Checkout
Timeline · 6 updates
-
investigating May 20, 2025, 12:24 PM UTC
We are currently investigating an issue that intermittently causes the checkout widget to load properly.
-
investigating May 20, 2025, 12:26 PM UTC
We are continuing to investigate this issue.
-
investigating May 20, 2025, 01:00 PM UTC
We are still investigating this issue. Please note that it appears to not affect all our customers that use our Checkout Widget.
-
monitoring May 20, 2025, 01:24 PM UTC
The investigation has identified that the reported issue is isolated to a small subset of our customer base. Findings indicate an issue with the site integration with our Checkout widget. Not a site-wide outage of the Checkout widget. The continued mitigation of those issues will be conducted with affected parties.
-
monitoring May 20, 2025, 01:30 PM UTC
We are continuing to monitor for any further issues.
-
resolved May 20, 2025, 03:58 PM UTC
No issues identified in our Checkout widget. Dialogues has been held with parties that experienced issues to have a look at the integration points. Please note that this is a late update of resolution and the status page will later be adjusted with proper timestamps. We wish you a great Wednesday evening.
Read the full incident report →
