nShift Outage History

nShift is up right now

Pingoru has recorded 56 incidents for nShift: 56 in the last 12 months and 41 in the last 90 days.

Source: status.nshiftportal.com

56incidents recorded
56last 12 months
41last 90 days
4 hourstypical duration

Incidents, newest first

Notice September 1, 2026 Colissimo (FR - 629) timeouts 50m Colissimo

Started Sep 01, 2026, 01:22 PM UTC· resolved Sep 01, 2026, 02:12 PM UTC

  1. investigating Sep 01, 2026, 01:22 PM UTC

    Colissimo is currently experiencing issues on their side. More information can be found on their status page: https://status.colissimo.fr/

  2. resolved Sep 01, 2026, 02:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 1, 2026 DHL Parcel Spain (ES - 761) errors 2h 6m Carrier Connections

Started Sep 01, 2026, 08:04 AM UTC· resolved Sep 01, 2026, 10:10 AM UTC

  1. investigating Sep 01, 2026, 08:04 AM UTC

    All requests to DHL Parcel Spain (ES - 761) are currently returning errors. The carrier's support team has been contacted.

  2. monitoring Sep 01, 2026, 08:53 AM UTC

    All requests are successful at the moment. We will continue to monitor the situation before closing the incident.

  3. resolved Sep 01, 2026, 10:10 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 31, 2026 Fetch my stuff (FI - 909) errors 4h 38m Carrier Connections

Started Aug 31, 2026, 05:41 AM UTC· resolved Aug 31, 2026, 10:20 AM UTC

  1. investigating Aug 31, 2026, 05:41 AM UTC

    All requests to Fetch my stuff (FI - 909) are currently returning errors. The carrier's support team has been contacted.

  2. monitoring Aug 31, 2026, 08:40 AM UTC

    All requests are successful at the moment and have been for the past 30 minutes. We will continue to monitor the situation before closing the incident.

  3. resolved Aug 31, 2026, 10:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 28, 2026 Bring INTL (442) timeouts 9h 30m Bring

Started Aug 28, 2026, 12:09 PM UTC· resolved Aug 28, 2026, 09:39 PM UTC

  1. investigating Aug 28, 2026, 12:09 PM UTC

    The majority of PUDO requests to Bring are currently timing out. The carrier's support team has been contacted.

  2. monitoring Aug 28, 2026, 12:39 PM UTC

    There have been no timeouts for the past 30 minutes. We will continue monitoring before closing the incident.

  3. monitoring Aug 28, 2026, 01:08 PM UTC

    Timeouts for Bring PUDO have reoccurred. We will continue monitoring the situation.

  4. monitoring Aug 28, 2026, 01:37 PM UTC

    Bring have acknowledged the issue and are working on a fix. We will provide an update as soon as we receive further information.

  5. resolved Aug 28, 2026, 09:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 6, 2026 Address Lookup Webservice 5m Rest API v1, Rest API v2, ShipAPI, Ticket and 1 more

Started Aug 06, 2026, 09:48 AM UTC· resolved Aug 06, 2026, 09:54 AM UTC

  1. identified Aug 06, 2026, 09:48 AM UTC

    Our address lookup webservice is currently experiencing issues. Our developers are aware and working on a fix.

  2. resolved Aug 06, 2026, 09:54 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 29, 2026 Colissimo (FR - 629) is currently experiencing issues. We have contacted the carriers' support. 27m Colissimo

Started Jul 29, 2026, 08:39 AM UTC· resolved Jul 29, 2026, 09:06 AM UTC

  1. investigating Jul 29, 2026, 08:39 AM UTC

    We are currently investigating this issue.

  2. resolved Jul 29, 2026, 09:06 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 27, 2026 DPD Service Disturbance 4h 30m Other carriers

Started Jul 27, 2026, 06:56 AM UTC· resolved Jul 27, 2026, 11:27 AM UTC

  1. investigating Jul 27, 2026, 06:56 AM UTC

    We are currently investigating the issue affecting DPD services with error DPD response: [ERROR: Input validation no valid GeoRouting database is found].

  2. investigating Jul 27, 2026, 08:35 AM UTC

    We are continuing to investigate this issue.

  3. identified Jul 27, 2026, 10:12 AM UTC

    A fix will be implemented: ETA aprox 1h. Thanks for your patience while we are working on this!

  4. monitoring Jul 27, 2026, 11:07 AM UTC

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

  5. resolved Jul 27, 2026, 11:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 17, 2026 OMNIVA shipment booking - degraded performance 1h 4m Omniva

Started Jul 17, 2026, 12:18 PM UTC· resolved Jul 17, 2026, 01:22 PM UTC

  1. investigating Jul 17, 2026, 12:18 PM UTC

    We have observed degraded performance (some request receiving the response after 15-20-25-30 seconds, while others are timing out) on Omniva shipment booking. The carrier has been contacted.

  2. monitoring Jul 17, 2026, 12:49 PM UTC

    The performance has recovered during the past 30 minutes, however the volume has reduced as well. We will monitor.

  3. resolved Jul 17, 2026, 01:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 8, 2026 Colissimo PUDO service 3h Drop Points, Colissimo

Started Jul 08, 2026, 07:55 AM UTC· resolved Jul 08, 2026, 10:56 AM UTC

  1. investigating Jul 08, 2026, 07:55 AM UTC

    Colissimo PUDO/Drop Point service is currently down.

  2. monitoring Jul 08, 2026, 08:56 AM UTC

    The service has been up again for 15 minutes. We will continue to monitor.

  3. resolved Jul 08, 2026, 10:56 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 6, 2026 DPD Global Meta API - 927 degraded performance 3h 31m Rest API v1

Started Jul 06, 2026, 07:13 AM UTC· resolved Jul 06, 2026, 10:44 AM UTC

  1. investigating Jul 06, 2026, 07:13 AM UTC

    DPD Global Meta API - 927 is currently experiencing issues. We have contacted the carriers' support.

  2. investigating Jul 06, 2026, 07:13 AM UTC

    We are continuing to investigate this issue.

  3. resolved Jul 06, 2026, 10:44 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 30, 2026 Schenker Sweden (SE - 0022) degraded performance 29m Schenker

Started Jun 30, 2026, 12:48 PM UTC· resolved Jun 30, 2026, 01:17 PM UTC

  1. investigating Jun 30, 2026, 12:48 PM UTC

    Shenker Sweden (22) is currently experiencing degraded performance on address check / booking requests. Some bookings go through, whilst others timeout. We have contacted their support.

  2. resolved Jun 30, 2026, 01:17 PM UTC

    The Schenker Sweden services performance has recovered.

Read the full incident report →

Major June 24, 2026 DAO Distribution (DK - 242) errors 6h 6m Other carriers, DAO Distribution

Started Jun 24, 2026, 08:20 AM UTC· resolved Jun 24, 2026, 02:26 PM UTC

  1. investigating Jun 24, 2026, 08:20 AM UTC

    Shipment booking requests towards DAO Distribution (DK - 242) are currently either returning errors or timing out. The carrier's support team has been contacted.

  2. identified Jun 24, 2026, 08:40 AM UTC

    DAO Distribution have acknowledged the issue and implemented a fix. However, we have received information that service interruptions might continue for the rest of the day.

  3. identified Jun 24, 2026, 09:38 AM UTC

    DAO Distribution have acknowledged the issue and implemented a fix. However, we have received information that service interruptions might continue for the rest of the day.

  4. monitoring Jun 24, 2026, 12:52 PM UTC

    DAO estimates no more downtime is expected for today. We will continue to monitor.

  5. resolved Jun 24, 2026, 02:26 PM UTC

    Since there have been no more interruptions on DAO services, we are closing this incident.

Read the full incident report →

Major June 22, 2026 Postnord DPD and DPD Baltics services disturbance 17m PostNord Sweden AB

Started Jun 22, 2026, 07:14 AM UTC· resolved Jun 22, 2026, 07:31 AM UTC

  1. investigating Jun 22, 2026, 07:14 AM UTC

    We are currently investigating the issue affecting Postnord DPD services with error DPD response: [ERROR: Input validation no valid GeoRouting database is found].

  2. monitoring Jun 22, 2026, 07:21 AM UTC

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

  3. resolved Jun 22, 2026, 07:31 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 18, 2026 DX API (GB - 0937) errors 2h 47m Carrier Connections

Started Jun 18, 2026, 08:03 AM UTC· resolved Jun 18, 2026, 10:51 AM UTC

  1. investigating Jun 18, 2026, 08:03 AM UTC

    All shipment booking requests towards DX API (GB - 0937) are currently returning errors. The carrier's support team has been contacted.

  2. identified Jun 18, 2026, 08:10 AM UTC

    DX API have acknowledged the issue and are working on a fix. We will continue to monitor the situation.

  3. resolved Jun 18, 2026, 10:51 AM UTC

    We are closing this incident, as all requests over the past hour have been successful.

Read the full incident report →

Major June 17, 2026 nShift Delivery - Postnord Sweden - Customs value issue 1h 55m PostNord Sweden AB

Started Jun 17, 2026, 07:50 AM UTC· resolved Jun 17, 2026, 09:45 AM UTC

  1. identified Jun 17, 2026, 07:50 AM UTC

    We are experiencing issues with Postnord Sweden services failing with the error "Customs value need to be more than 0.0 ". We are working on reverting the change that has caused this as soon as possible. We are sorry for any inconvenience this may have caused. In the meantime, there are two quick workarounds available if you need to make adjustments on your side: 1. Do not send a customs declaration when no customs declaration data needed (within EU) In practice, this means omitting the "customsDeclaration":{}, element entirely. If the field is omitted, the shipment will be processed successfully. 2. Send the customs declaration field with a null value instead. For example: "customsDeclaration":null, This will also allow the shipment to be processed successfully.

  2. monitoring Jun 17, 2026, 08:47 AM UTC

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

  3. resolved Jun 17, 2026, 09:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 15, 2026 GLS API (DK - 0951) timeouts 1h 38m GLS

Started Jun 15, 2026, 08:41 AM UTC· resolved Jun 15, 2026, 10:20 AM UTC

  1. investigating Jun 15, 2026, 08:41 AM UTC

    GLS API (DK - 0951) is timing out on most shipment booking requests. The carrier's support team has been contacted.

  2. identified Jun 15, 2026, 08:58 AM UTC

    GLS have acknowledged the issue and confirmed it is isolated to international labels. We are actively monitoring the situation.

  3. resolved Jun 15, 2026, 10:20 AM UTC

    We are closing this incident, as all requests over the past hour have been successful.

Read the full incident report →

Minor June 12, 2026 Danske Fragtmænd (DK - 10) sending edi timeouts 1h 37m Danske Fragtmænd

Started Jun 12, 2026, 08:14 AM UTC· resolved Jun 12, 2026, 09:52 AM UTC

  1. investigating Jun 12, 2026, 08:14 AM UTC

    Danske Fragtmænd (DK - 10) is currently experiencing issues with their ftp server. Sending edi towards ftp.fragt.dk will return a timeout error. The carrier's support team has been contacted.

  2. identified Jun 12, 2026, 08:22 AM UTC

    Danske Fragtmænd have acknowledged the issue and are working on a fix. We are actively monitoring the situation.

  3. monitoring Jun 12, 2026, 09:01 AM UTC

    Danske Fragtmænd have confirmed that their ftp is up and running. We will continue to monitor before closing the incident.

  4. resolved Jun 12, 2026, 09:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 11, 2026 BRT IT timeouts 2h 4m BRT

Started Jun 11, 2026, 01:05 PM UTC· resolved Jun 11, 2026, 03:09 PM UTC

  1. identified Jun 11, 2026, 01:05 PM UTC

    BRT Italy is returning timeouts. We are currently waiting for an answer from the carrier.

  2. identified Jun 11, 2026, 01:59 PM UTC

    BRT have acknowledged the incident, but are unable to provide a timeline for a fix.

  3. monitoring Jun 11, 2026, 02:43 PM UTC

    All requests are successful at the moment. We will continue to monitor the situation before closing this incident.

  4. resolved Jun 11, 2026, 03:09 PM UTC

    We consider this incident closed as there have been no errors for the last 60 minutes.

Read the full incident report →

Major June 11, 2026 DSV Road Sweden (legacy DB Schenker Sverige) experiencing issues 7h 38m DB Schenker, Schenker

Started Jun 11, 2026, 11:05 AM UTC· resolved Jun 11, 2026, 06:44 PM UTC

  1. investigating Jun 11, 2026, 11:05 AM UTC

    We are currently investigating this issue.

  2. investigating Jun 11, 2026, 11:08 AM UTC

    We are continuing to investigate this issue.

  3. identified Jun 11, 2026, 12:27 PM UTC

    DSV Road Sweden is still unable to provide an estimated timeline for resolving the issue. We're awaiting further updates and will share additional information as soon as it becomes available.

  4. resolved Jun 11, 2026, 06:44 PM UTC

    We are closing this incident as there haven't been any errors in the last hour.

Read the full incident report →

Critical June 10, 2026 Asendia Sync (988) Gateway Errors 1h 35m Asendia

Started Jun 10, 2026, 01:21 PM UTC· resolved Jun 10, 2026, 02:56 PM UTC

  1. identified Jun 10, 2026, 01:21 PM UTC

    Carrier Asendia Sync (988) is returning 504 Gateway error on most requests. We haven't yet heard back from them this time around.

  2. monitoring Jun 10, 2026, 01:33 PM UTC

    All requests are now receiving a valid response from Asendia. We will continue to monitor for a longer period.

  3. resolved Jun 10, 2026, 02:56 PM UTC

    We are closing this incident as all requests in the last hour and a half have been successful.

Read the full incident report →

Major June 10, 2026 Asendia Sync (988) timeouts 2h 52m Asendia

Started Jun 10, 2026, 08:32 AM UTC· resolved Jun 10, 2026, 11:25 AM UTC

  1. investigating Jun 10, 2026, 08:32 AM UTC

    Carrier Asendia Sync (988) is currently experiencing issues, shipment booking requests towards their endpoint are timing out. The carrier's technical support has been contacted.

  2. identified Jun 10, 2026, 08:48 AM UTC

    Asendia have acknowledged the issue and are working on a fix. We are actively monitoring the situation.

  3. monitoring Jun 10, 2026, 10:41 AM UTC

    Asendia have confirmed that the service is up and running. We will continue to monitor before closing the incident.

  4. resolved Jun 10, 2026, 11:25 AM UTC

    We are closing this incident as there have been no more errors.

Read the full incident report →