Inside the network desk: how a 02:00 UTC reroute actually works

A blocked berth in Singapore, three phone calls and a re-cut booking — walked through hour by hour.

SEC / 01 Overview

Introduction

At two in the morning UTC a berth in Singapore went unavailable and forty-one containers stopped being a schedule and started being a decision. This is what the next four hours looked like from the network desk, hour by hour, including the call we got wrong.

Hour One: Confirming, Not Reacting

The first alert came from the carrier feed, the second from the terminal. Neither is authoritative on its own. The desk called the agent before touching a booking, because a re-cut made on a false signal costs more than twenty minutes of waiting.

Hour Two And Three: Re-cutting

Nine containers had a fixed retail set date and moved to the next available string via Port Klang. The remaining thirty-two had float and stayed put. Splitting the shipment cost less than upgrading all forty-one, and the client approved it by message at 04:12.

Hour Four: Telling People

Every affected consignee had a revised ETA before their working day started. Nobody found out from a tracking page. That is the part of the process we consider non-negotiable.

Inside the network desk: how a 02:00 UTC reroute actually works

2/6

days door-to-door

Transit

02:00

Cut-off

countries

Coverage

What We Got Wrong

We re-cut two boxes that did not need it, because the float figure in our system was three days stale. The rule changed the same week: float is confirmed with the planner, never read from cache.

A—02

A person, before the tracking page

Every affected consignee had a revised ETA and a reason before their working day started — no client discovered the delay from a status feed.

What's included

24/7 network desk monitoring

Multi-source disruption verification

Priority re-cut on alternative strings

Proactive consignee notification

Post-incident review within 48 hours

Conclusion

Reroutes are not exceptional; they are a Tuesday. What separates a good desk from a bad one is whether the client hears it from a person before they see it on a screen.