pingoru pingoru nShift had 41 outages in the last 2 years totaling 96h 8m of downtime, averaging 1.7 incidents per month.
There were 41 nShift outages since June 10, 2026 totaling 96h 8m of downtime. Each is summarised below. Incident details, duration, and resolution information.
The carrier identified a problem on their end and are working on a solution.
Requests with CheapCargo have been receiving expected responses, returning package/shipment numbers in a timely fashion. We will be monitoring.
This incident has been resolved.
We are currently investigating this issue.
DPD is currently aware of ongoing issues and the matter is under active investigation.
This incident has been resolved.
We are currently investigating this issue.
Correos is aware about the increased response times and timeouts, and are currently working on resolving this issue.
The Correos endpoint has started to respond within expected parameters. We are monitoring.
This incident has been resolved.
We are currently investigating this issue.
Approximately 5% of the PostNord Price Calculation requests are timing out. We are monitoring and awaiting feedback from the carrier.
This incident has been resolved.
DSV is experiencing intermittent issues on their FTP server. Customers might see the error "The connection was closed by the server. Make sure you are connecting to an SSH or SFTP server." while attempting to send EDI data towards the DSV FTP. This is only affecting sending EDI data, bookings are working as expected. The issue is intermittent - thus retrying can temporarily overcome the issue. The carrier has been contacted.
DSV has confirmed experiencing some fluctuations in the SFTP on EDI and that their team is working hard to resolve it.
This incident has been resolved.
Following the prolonged unavailability on DSV XPress bookings, which the carrier has fixed for the past 2h, we are now seeing errors while trying to transmit data towards the DSV FTPs. We are in contact with the carrier.
This incident has been resolved.
We are currently investigating this issue.
The DSV XPress IT department is aware and working on a fix. No ETA has been provided at this point.
Successful requests with DSV XPress have started to flow in. We will be monitoring for the next period.
DSV XPress is experiencing another service outage following a brief recovery.
This incident has been resolved.
DPD Global / Meta API (INT - 927) is currently experiencing intermittent timeouts, returning error: Service Unavailable [503]. So far, approximately 30% of the requests made with this carrier are encountering issues, whilst we have successful ones in parallel. We have contacted the carrier and will be monitoring.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
This incident has been resolved.
All PUDO requests to Colissimo (FR - 629) are currently timing out. The carrier's support team has been contacted.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We have identified a issue with calls towards DHL Parcel DE. This is after a change done on the carrier end today. We are working now on a fix and should have it resolved shortly.
A fix has now been deployed and confirmed working. All DHL booking go through with no errors. Will continue to monitor through the night.
GLS (NL – 460) is currently experiencing issues. We have already contacted the carrier’s support team and are currently waiting for further updates from them.
This incident has been resolved.
We are currently investigating an issue affecting communication with several carriers, which may impact Checkout and shipment creation in Delivery. We are actively working on a resolution and will share updates as soon as they're available.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
PUDO requests to BRT are returning "(503) Service Unavailable" errors. We have contacted the carrier's support team.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
All shipment booking requests to TNT (249) are timing out. The carrier's support team has been contacted.
We are continuing to investigate this issue.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
At the moment we are seeing an increase in errors towards FedEx 977 integration. These now error with TOTALCUSTOMSVALUE.REQUIRED - Customs Value is required field. We have contacted the carrier and are working on a solution with them currently.
We have deployed a fix and are seeing successful requests across the board. Will continue to monitor.
We have not seen any more error since the fix. The service is now working properly.
Colissimo is currently experiencing issues on their side. More information can be found on their status page: https://status.colissimo.fr/
This incident has been resolved.
All requests to DHL Parcel Spain (ES - 761) are currently returning errors. The carrier's support team has been contacted.
All requests are successful at the moment. We will continue to monitor the situation before closing the incident.
This incident has been resolved.
All requests to Fetch my stuff (FI - 909) are currently returning errors. The carrier's support team has been contacted.
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.
This incident has been resolved.
The majority of PUDO requests to Bring are currently timing out. The carrier's support team has been contacted.
There have been no timeouts for the past 30 minutes. We will continue monitoring before closing the incident.
Timeouts for Bring PUDO have reoccurred. We will continue monitoring the situation.
Bring have acknowledged the issue and are working on a fix. We will provide an update as soon as we receive further information.
This incident has been resolved.
Our address lookup webservice is currently experiencing issues. Our developers are aware and working on a fix.
This incident has been resolved.