Felixstowe’s average berthing delay reached 49.0 hours in the two weeks to November 15, up 36.0 hours on the previous two weeks, according to the Tradlinx Port Congestion Index. Shenzhen rose 4.2 hours over the same period. Jebel Ali moved the other way, falling 15.5 hours.
Changes like these don’t reach the lead time in an ERP unless someone updates it. A planned lead time is one fixed number per lane, and if it was set from carrier schedules months ago, it now understates the wait at ports that have congested or carries buffer you no longer need at ports that have cleared. Either way the error costs money, through stockouts and expedited freight on lanes that run short and excess stock on lanes that are padded.
Your container milestones record what each lane actually takes. Below is what the latest port data shows, and how to recalibrate planned lead times from your own shipment data.
What Two Weeks of Port Data Show
| Port | Oct 19 to Nov 1 | Nov 2 to 15 | Change | Level now |
|---|---|---|---|---|
| Felixstowe | 13.0h | 49.0h | +36.0h | CONGESTED (was STABLE) |
| Vancouver | 14.1h | 21.2h | +7.1h | BUSY (was STABLE) |
| Nhava Sheva | 13.3h | 19.1h | +5.8h | BUSY (was STABLE) |
| Shenzhen | 8.5h | 12.7h | +4.2h | CONGESTED |
| Port Klang | 23.4h | 23.4h | 0.0h | CONGESTED (was BUSY) |
| Jebel Ali | 28.5h | 13.0h | -15.5h | STABLE (was BUSY) |
The moves run in both directions, and several are large against a lead time usually planned in whole days. Port Klang shows a different pattern: its delay held at 23.4 hours while its overall congestion level worsened, so a flat delay figure does not always mean a lane is steady.
Two Lanes Moving in Opposite Directions
A lane’s planned ocean lead time usually rolls several stages into one number: time at the origin terminal, waiting to berth, the sea passage, any transshipment, waiting to berth at destination, and discharge to pickup. Carrier schedules publish the sea passage. Berthing waits at either end stay outside that figure until they show up as a late arrival.
Shenzhen to Felixstowe. In the two weeks to November 1, average berthing waits at the two ends added up to 21.5 hours. In the two weeks to November 15 they added up to 61.7 hours, an increase of 40.2 hours, or about 1.7 days, before any change at sea or at transshipment. A lead time set before that change includes none of it.
Lanes into Jebel Ali. The average berthing delay fell from 28.5 to 13.0 hours. If planners padded lead times on these lanes during the earlier congestion, the padding now triggers orders earlier than needed, and the result sits in the warehouse as extra stock.
Port waits also compound with late sailings. Sea-Intelligence put global schedule reliability at 50.6% in September, with late vessels arriving an average of 6.65 days behind schedule.
Berthing Delay Is One Part of the Gap
The Port Congestion Index measures how long vessels wait before berthing, averaged across all vessels calling at a port. Your containers can fare better or worse than that average. On a weekly service, a rolled container can add roughly a week or longer, as covered in how to tell a rollover from a vessel delay, and transshipment dwell and terminal time after discharge add more.
The measure that captures the whole gap for your lanes is the elapsed time between your own container milestones, from gate-in at origin to gate-out at destination. When the ERP keeps a fixed lead time while those stages move, planners usually learn about it from a stockout or an expedite request.
If planned lead times in your ERP still come from carrier schedules, walk through how teams feed actual transit times from container milestones into their planning systems.

How to Recalibrate Lead Times From Shipment Data
- Pull 6 to 12 months of container milestones per lane and carrier, measured from gate-in at origin to gate-out at destination.
- Compare the median and the spread of actual times with the planned lead time on each lane. Safety stock depends on the spread, so a lane with the right average and wide variation still needs attention. Why an average cannot size a buffer covers this in more detail.
- Break the actual time into stages to see which one moved: origin dwell, berthing waits, sea passage, transshipment and destination dwell.
- Set a review trigger on berthing delay at the ports on each lane, for example a change of more than 24 hours in the two-week average.
- Set a review cadence, such as monthly for volatile lanes and quarterly for stable ones, or update lead times automatically through an integration with your planning system.
Checklist Before the Next Planning Cycle
- List the origin and destination ports on each lane and check their latest two-week berthing delay.
- Flag lanes where the combined change at both ends exceeds your review trigger.
- Compare planned lead time with the actual median and spread from container milestones.
- Separate rollovers from vessel delays before counting them in lead-time variation.
- Lower lead times on lanes where ports have cleared, as well as raising them where delays grew.
- Record the date each lead time was last updated.
Further Reading
- Tradlinx: Global Port Congestion Index, data as of 15 November 2026
- FreshPlaza: Global shipping schedule reliability improves to 50.6% in September (Sea-Intelligence)
Sources: berthing delay figures are two-week averages from the Tradlinx Port Congestion Index, data as of 15 November 2026, comparing 2 to 15 November with 19 October to 1 November. Previous-period values for Felixstowe, Vancouver and Nhava Sheva are derived from the reported change. Schedule reliability figures are from Sea-Intelligence’s Global Liner Performance report for September 2026. Port averages cover all vessels calling at a port and may differ from your own shipments.
Need help interpreting this disruption or your shipment?
For a quick question, chat with Tradlinx on WhatsApp. For a deeper discussion, book a time below.




Leave a Reply