Carrier Server - degraded performance

Incident Report for nShift

Postmortem

Postmortem: Carrier booking disruption, 19 November 2026

What happened
On 19 November between 10:53 and 11:22 CET (09:53–10:22 UTC), most shipment bookings through our Shared Carrier Services failed or timed out. Delivery options in nShift Checkout loaded more slowly during the same period.
All services have been fully operational since 11:22 CET.

Why it happened
An unexpected load spike on one of our production databases slowed CarrierServer's responses.
Booking requests queued up faster than the service could recover on its own, and full service returned once our team brought additional capacity online.

What we have done

  • Found the exact cause and taken immediate steps to stop it from recurring.
  • Increased CarrierServer capacity, giving the service significantly more headroom than before.
  • Added deeper database monitoring, so we can spot and resolve this kind of situation faster.

Ready for Black Friday
We know the coming weeks are the most important of the year for your business.
Ahead of Black Friday and Cyber Monday, our booking services are running with extra capacity and heightened monitoring.
Additional safeguards are being rolled out to keep heavy database activity away from live booking traffic and to make our platform recover automatically and faster.
Our focus is on keeping your peak season running smoothly.

If you saw failed bookings between 10:53 and 11:22 CET, please retry them, and contact our support team if anything looks incorrect. We are sorry for the disruption and thank you for your patience.

Posted Nov 19, 2026 - 13:18 CET

Resolved

Following our monitoring, we have not detected any new issues. This incident is resolved.
Posted Nov 19, 2026 - 12:43 CET

Monitoring

The implemented fix is stable. We continue monitoring.
Posted Nov 19, 2026 - 12:04 CET

Update

We are continuing to investigate the root cause. The system is operational now.
Posted Nov 19, 2026 - 11:40 CET

Update

We have increased our number of machines for Carrier Server, which has stabilised production for the time-being, whilst we investigate the cause.
Posted Nov 19, 2026 - 11:31 CET

Investigating

We have identified increased response times and time outs, on our Carrier Server. We are currently investigating.
Posted Nov 19, 2026 - 11:14 CET
This incident affected: Ship (Carrier Server).