Ingrid Outage History

Ingrid is up right now

Ingrid had 35 outages in the last 2 years totaling 10h 48m of downtime — averaging 1.4 incidents per month.

There were 35 Ingrid outages since July 26, 2024 totaling 10h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://ingrid.statuspage.io

Critical May 15, 2025

Returns Portal Access issue

Detected by Pingoru
May 15, 2025, 06:11 AM UTC
Resolved
May 15, 2025, 06:54 AM UTC
Duration
43m
Affected: Returns
Timeline · 3 updates
  1. investigating May 15, 2025, 06:11 AM UTC

    We have recently identified an error in the system that affects the Returns Portal. 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. monitoring May 15, 2025, 06:51 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.

  3. resolved May 15, 2025, 06:54 AM UTC

    The incident has now been resolved and the Returns Service is operational

Read the full incident report →

Minor May 15, 2025

Issues to connect to Best Transpost API

Detected by Pingoru
May 15, 2025, 06:05 AM UTC
Resolved
May 15, 2025, 08:55 AM UTC
Duration
2h 50m
Affected: Transport Administration
Timeline · 3 updates
  1. identified May 15, 2025, 06:05 AM UTC

    We have identified that there are issues to communicate with the API for Best Transport, which affects shipment bookings. We have contacted carrier about this.

  2. monitoring May 15, 2025, 08:16 AM UTC

    As of around 09:45 the communication has been working as expected with Best Transport API. We will continue to monitor this.

  3. resolved May 15, 2025, 08:55 AM UTC

    This incident is resolved. No further issues to connect to Best Transport API.

Read the full incident report →

Critical April 22, 2025

PostNord Booking Service Disruption

Detected by Pingoru
Apr 22, 2025, 07:50 AM UTC
Resolved
Apr 22, 2025, 08:18 AM UTC
Duration
27m
Affected: Transport Administration
Timeline · 4 updates
  1. investigating Apr 22, 2025, 07:50 AM UTC

    We are currently investigating an issue causing failures in the PostNord booking service. The disruption is resulting in unsuccessful booking attempts for shipments via PostNord. Further information will be shared as soon as we have a clearer picture of the underlying problem and its scope.

  2. identified Apr 22, 2025, 07:52 AM UTC

    The issue affecting PostNord was confirmed on their side. Their systems were experiencing disruptions earlier, which impacted shipment bookings.

  3. monitoring Apr 22, 2025, 07:54 AM UTC

    A fix has been deployed by PostNord, and we are currently monitoring the solution to ensure continued stability and performance.

  4. resolved Apr 22, 2025, 08:18 AM UTC

    This incident has been resolved

Read the full incident report →

Major March 16, 2025

Airmee API down

Detected by Pingoru
Mar 16, 2025, 04:03 PM UTC
Resolved
Mar 16, 2025, 05:21 PM UTC
Duration
1h 17m
Affected: API Connectivity
Timeline · 3 updates
  1. investigating Mar 16, 2025, 04:03 PM UTC

    As of around 1605 today Airmee started to return null messages to our requests. We are currently monitoring the connection and trying to connect with Airmee what the status of getting it back up and running is.

  2. monitoring Mar 16, 2025, 04:21 PM UTC

    We are currently monitoring the API connection and awaiting response from Airmee for the status of resolving this issue

  3. resolved Mar 16, 2025, 05:21 PM UTC

    We are no longer seeing any errors connected with the Airmee API as of 17:51, we will continue to monitor the issues for another 30 minutes to confirm the resolution of the issue

Read the full incident report →

Major February 21, 2025

Incident: UPS REST API Issues

Detected by Pingoru
Feb 21, 2025, 07:34 AM UTC
Resolved
Feb 21, 2025, 09:50 AM UTC
Duration
2h 16m
Affected: Transport Administration
Timeline · 6 updates
  1. investigating Feb 21, 2025, 07:34 AM UTC

    We have recently identified an error in the system that affects (UPS Booking (TA) ). 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 Feb 21, 2025, 07:41 AM UTC

    It has been identified that the UPS API has a current outage and the solution is being investigated. Updates will follow shortly

  3. identified Feb 21, 2025, 07:51 AM UTC

    We have recieved confirmation that the UPS has escalated the incident and are working on a solution to their REST API to restore services We are currently awaiting a status update from the carrier

  4. identified Feb 21, 2025, 09:02 AM UTC

    The global UPS outage is still ongoing, and the UPS team is actively working to resolve the issue. We will continue to provide updates as progress is made.

  5. monitoring Feb 21, 2025, 09:15 AM UTC

    Ongoing monitoring of the REST API indicates that the service has been restored. We are now awaiting confirmation from the carrier to verify full restoration.

  6. resolved Feb 21, 2025, 09:50 AM UTC

    The incident has now been marked as resolved UPS REST API was officially restored at 10:07

Read the full incident report →

Critical December 19, 2024

Incident Protocol Initiated: Bring Booking

Detected by Pingoru
Dec 19, 2024, 10:45 AM UTC
Resolved
Dec 19, 2024, 11:43 AM UTC
Duration
58m
Affected: Transport Administration
Timeline · 5 updates
  1. investigating Dec 19, 2024, 10:45 AM UTC

    We have recently identified an error in the system that affects Bring Booking. 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. investigating Dec 19, 2024, 10:56 AM UTC

    Prio: Critical Scope: Bring Booking API Update: Bring is working to restore booking services

  3. identified Dec 19, 2024, 10:59 AM UTC

    We are currently waiting for confirmation from the carrier (Bring) when Booking Services have been restored

  4. monitoring Dec 19, 2024, 11:07 AM UTC

    The error appears to have been resolved. We are currently monitoring booking for Bring and will update here as we confirm the resolution of this incident.

  5. resolved Dec 19, 2024, 11:43 AM UTC

    The incident has now been resolved

Read the full incident report →

Minor December 12, 2024

PostNord API Issue

Detected by Pingoru
Dec 12, 2024, 10:28 AM UTC
Resolved
Dec 12, 2024, 11:23 AM UTC
Duration
54m
Affected: Transport Administration
Timeline · 6 updates
  1. investigating Dec 12, 2024, 10:28 AM UTC

    We are currently investigating booking disruptions for PostNord

  2. identified Dec 12, 2024, 10:53 AM UTC

    PostNord has acknowledged ongoing service disruptions affecting Varubrev

  3. monitoring Dec 12, 2024, 11:11 AM UTC

    API stability has been restored. Booking errors have ceased and we are actively monitoring API performance

  4. monitoring Dec 12, 2024, 11:13 AM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Dec 12, 2024, 11:15 AM UTC

    We are continuing to monitor for any further issues.

  6. resolved Dec 12, 2024, 11:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 26, 2024

Authentication issue

Detected by Pingoru
Nov 26, 2024, 03:42 PM UTC
Resolved
Nov 26, 2024, 04:45 PM UTC
Duration
1h 2m
Affected: API ConnectivityIngrid Merchant Platform
Timeline · 2 updates
  1. identified Nov 26, 2024, 03:42 PM UTC

    We have identified an authentication issue from internal testing. We have no evidence to believe that this has been exploited.

  2. resolved Nov 27, 2024, 12:02 PM UTC

    This incident has been resolved. This issue affected users of our In-Store product and has now been resolved.

Read the full incident report →

Notice October 28, 2024

IP Maintenance Notification

Detected by Pingoru
Oct 28, 2024, 10:08 AM UTC
Resolved
Oct 28, 2024, 10:08 AM UTC
Duration
—
Affected: API Connectivity
Timeline · 1 update
  1. resolved Oct 28, 2024, 10:08 AM UTC

    We will be performing maintenance on our production and stage environments Monday, October 28th, in the morning. Our goal is to complete the process smoothly without any downtime. As part of this maintenance, we will be changing IP address to our environment. The new IP addresses are as follows: Stage environment: 34.54.164.202 Production environment: 34.36.165.186 If you have whitelisted our current (old) IPs, please ensure that you add the new ones to your whitelist. The old IPs (104.199.16.61, 35.187.14.136) may still be in use up until Monday, November 4th.

Read the full incident report →

Minor August 21, 2024

Incident Protocol Initiated - Porterbuddy

Detected by Pingoru
Aug 21, 2024, 09:37 AM UTC
Resolved
Aug 21, 2024, 09:55 AM UTC
Duration
17m
Affected: Transport Administration
Timeline · 4 updates
  1. investigating Aug 21, 2024, 09:37 AM UTC

    We have recently identified an error with Porterbuddies services being down. We will inform you as we get more information from Porterbuddy on the investigation and resolution of the issues

  2. identified Aug 21, 2024, 09:40 AM UTC

    Prio: High Scope: All Budbee and Porterbuddy services Update: The issues stem from an issue with the Budbee API which also affects Porterbuddy

  3. monitoring Aug 21, 2024, 09:46 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.

  4. resolved Aug 21, 2024, 09:55 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 →