nShift TMS Outage History
19 incidents recorded over the last 365 days, 10 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded nShift TMS Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 25, 2026 | Deploy of 2026.04 releaseThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Oct 22, 2026 | DSV (ex Schenker) - timeoutsThis incident has been resolved. DSV confirmed a fix at 09:20 CEST, and we have not observed any errors since. Bookings and other requests to DSV (ex Schenker) are working as expected. | 2h 57m | Resolved |
| Sep 14, 2026 | FTP file processing issueThis incident has been resolved. | 24h 54m | Resolved |
| Sep 8, 2026 | TNT Express connection issuesBooking requests to TNT Express are completing successfully and no further errors have been observed since 15:07. | 5h 9m | Resolved |
| Sep 6, 2026 | Deploy of 2026.03 releaseThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Jun 26, 2026 | Issue booking PUDO shipments through integrationThis incident has been resolved. | 2h 21m | Resolved |
| May 10, 2026 | Deploy of 2026.02 releaseThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Apr 27, 2026 | Disturbance in servicePerformance has remained stable since yesterday following mitigation efforts. The incident is now considered resolved. We will continue to monitor the system closely. | 48h 0m | Resolved |
| Apr 26, 2026 | AWS Migration (continued)The scheduled maintenance has been completed. | 40 min | Scheduled |
| Apr 26, 2026 | AWS MigrationThe scheduled maintenance has been completed. | 2h 30m | Scheduled |
| Apr 12, 2026 | DB Index UpdateThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Mar 20, 2026 | Issues with Multi-Recipient EmailsThe issue has been mitigated and the impact has been significantly reduced. We have put temporary solutions in place to address the issue while a permanent fix is being prepared for deployment next week. We will… | 146h 44m | Resolved |
| Feb 8, 2026 | Deploy of Release 2026.01The scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Feb 2, 2026 | Timeouts on various carrier connectionsAll services are operational with no errors detected. | 1h 24m | Resolved |
| Dec 19, 2025 | Status page update: removal of Delivery componentsThe scheduled maintenance has been completed. | 1 min | Scheduled |
| Dec 14, 2025 | Deploy of 2025.04-01 minor releaseThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Dec 11, 2025 | DHL API Performance IssuesThis incident has been resolved. | 2h 56m | Resolved |
| Dec 10, 2025 | Disturbance in serviceOn December 10, 2025, between 13:57 CET and 15:53 CET, some clients experienced intermittent issues when booking shipments due to degraded system performance. The root cause was a spike in resource usage within our… | 2h 42m | Resolved |
| Dec 5, 2025 | Service degradationThis incident has been resolved. We have not found or received reports about any issues related to the incident other than our support tool being down for a period of time. | 1h 49m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next nShift TMS incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This nShift TMS Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before nShift TMS acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single nShift TMS outage in this window ran 6d 2h, against a mean recovery of 13h 38m. If you depend on nShift TMS in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.