Vessels calling at PSA Singapore are facing berth waits of three to five days, with some waiting considerably longer. Kuehne+Nagel reported on October 9 that vessels carrying large volumes of transshipment discharge cargo may face longer waits, while export-heavy vessels may receive higher berthing priority as PSA manages pressure on its nearly full yards.
For importers and forwarders with containers relaying through Singapore, the vessel carrying each container matters. A discharge-heavy call may face additional anchorage delays, putting onward connections at risk. The port-wide congestion average cannot show which individual vessels are most exposed, making first-leg vessel status and onward connection confirmation particularly important.
What PSA Singapore Is Doing Differently
Severe congestion has built up at PSA Singapore over several weeks, and yard capacity is reportedly close to full utilization. With limited yard space available, PSA is managing berthing priorities partly around cargo volumes and their impact on terminal capacity.
Vessels scheduled to discharge significantly more transshipment containers than they load for export may be required to remain at anchorage longer. Export-heavy calls may receive higher priority, while PSA is seeking to limit additional transshipment cargo entering its terminals.
The operational logic is tied to yard utilization. A call that loads more containers than it discharges can relieve pressure on a crowded terminal, while a discharge-heavy call adds containers that must be stored, sorted and transferred to onward services. The reported berthing priorities suggest that this difference may influence waiting times, although no fixed rule applying to every vessel has been established.
The report attributes the pressure to strong carrier demand ahead of Golden Week and accumulated roll pools, with elevated congestion expected to continue in the weeks ahead.
What the Singapore Numbers Show
Singapore entered the CONGESTED band in the latest Tradlinx Port Congestion Index. The readings below come from two sources that measure different aspects of vessel performance over different periods.
| Measure | Reading | Source and period |
|---|---|---|
| Waiting time before berth | 3 to 5 days, longer for some vessels | Kuehne+Nagel, October 9, 2026 |
| Average vessel arrival delay (estimated vs. actual arrival) | 4.48 days | Kuehne+Nagel seaexplorer, 30 days to October 9 |
| Average vessel departure delay | 4.3 days | Kuehne+Nagel seaexplorer, 30 days to October 9 |
| Vessels alongside / at anchorage | 55 / 11 | Kuehne+Nagel, October 9 snapshot |
| Congestion rating | CONGESTED (entered this edition) | Tradlinx PCI, Sep 22 – Oct 5, 2026 |
| Two-week berthing delay | 11.2 hours (up 1.3 hours) | Tradlinx PCI, Sep 22 – Oct 5, 2026 |
| Vessels waiting | 44 | Tradlinx PCI, Sep 22 – Oct 5, 2026 |
PSA Singapore congestion readings. The sources use different measures, vessel populations and time windows, so the figures are not directly comparable.
The 4.48-day average arrival delay measures how late vessels arrive against their estimated arrival times. That includes delays accumulated before reaching Singapore. The reported three-to-five-day berth waits describe the anchorage situation affecting vessels at PSA.
The PCI’s 11.2-hour figure is a two-week port-level berthing-delay reading, covering an earlier observation period. Differences in methodology, reporting windows and vessel populations can produce substantially different results.
There is also an operational distinction worth watching. A vessel’s discharge and loading profile may influence how long it waits for a berth. That means containers on different vessels can face very different connection risks even when they pass through the same port.
For shipment planning, the specific vessel’s status and its onward connection provide information that the port-wide average cannot.
Which Containers Carry the Risk
The vessels potentially most exposed are those arriving in Singapore to discharge large volumes of relay cargo for transfer onto other services.
A transshipment container must be discharged from its first-leg vessel before it can connect with its onward sailing. If the inbound vessel faces a prolonged anchorage wait, the container may reach the terminal too late for its planned connection.
Exposure sits on both sides of the connection:
- Inbound leg. A vessel with a large transshipment discharge volume may wait longer at anchorage. The delayed berth can postpone container discharge and threaten its planned onward connection.
- Onward leg. Containers already discharged into the yard can also face delays. Accumulated roll pools add to the risk that some containers may be pushed onto later sailings even after reaching Singapore.
- Rerouting. PSA’s reported efforts to limit additional transshipment intake may prompt carriers to consider alternative relay arrangements. Nearby hubs are not uniformly clear. In the Sep 22 – Oct 5 PCI, Tanjung Pelepas was also CONGESTED with 75 vessels waiting, while Colombo eased to BUSY after its delay fell by 20.6 hours.
The cited update does not identify specific carrier rerouting decisions. Any proposed change needs to be confirmed against the carrier’s actual service plan and the conditions at the alternative hub.
Where Visibility Breaks: The Transshipment Connection
In July we looked at how a hub can read calm on vessel metrics while transshipment cargo waits between legs. Singapore now faces additional pressure at the berth itself, with discharge-heavy vessels potentially waiting longer before their containers can enter the terminal.
That creates a problem for shipment monitoring. A container can lose its planned onward connection when the inbound vessel is delayed, but its tracking record may not immediately show a revised second-leg assignment or delivery estimate.
Missing ETA information is a separate, documented visibility problem. In a Tradlinx analysis of 508,055 ocean container shipments, carrier ETAs were blank in 8.43% of shipments, and transshipment cargo accounted for 87% of those gaps. The largest individual category was the ETA for the intermediate transshipment port, missing on 6.09% of all shipments.
Those findings come from a global shipment sample with actual arrivals confirmed by March 2026. They do not measure the effect of Singapore’s October congestion, but they establish how frequently ETA visibility is incomplete around transshipment movements.
For a Singapore relay container, the immediate warning may be an inbound vessel still at anchorage after its expected berthing time. After that, an unchanged onward vessel assignment, a stale ETA or a missing arrival estimate should trigger closer investigation. A shipment record that has not changed does not necessarily mean the connection remains intact.
If your team is checking carrier portals booking by booking to work out which Singapore relay containers have lost their connection, walk through how ops teams flag transshipment exceptions across carriers.
What to Re-Check on Singapore-Routed Shipments
- Identify Singapore relay cargo. List every open container whose routing includes Singapore as a transshipment port, including shipments where Singapore is not the final destination.
- Identify the inbound vessel. Record the first-leg vessel and its latest expected arrival and berthing status. Where available, ask the carrier or forwarder whether the call is affected by discharge-heavy berthing constraints.
- Check anchorage delays. Compare the vessel’s actual arrival and berthing events against its planned schedule. For a vessel still waiting at anchorage, assess whether the remaining time is sufficient to protect the onward connection.
- Verify the onward leg. Confirm that the assigned second-leg vessel and ETA are still valid. Treat a missing, stale or unchanged onward ETA on a delayed inbound movement as an exception requiring investigation.
- Confirm loading after discharge. A container reaching the Singapore yard has not necessarily secured its onward sailing. Check whether the planned vessel assignment remains valid and obtain loading confirmation when available.
- Evaluate alternative hubs. If a carrier or forwarder proposes rerouting relay cargo, check current congestion at the alternative hub and confirm the revised sailing and connection arrangements.
- Revise delivery commitments. Use the latest confirmed onward vessel assignment and sailing schedule when updating delivery estimates. The inbound vessel’s anchorage delay alone may not capture the additional time lost if a connection is missed.
Further Reading
- PSA Singapore congestion persists as vessel arrival delay reaches 4 days (Kuehne+Nagel)
- Tradlinx Port Congestion Index, Sep 22 – Oct 5, 2026 (Tradlinx)
Sources and dates: Singapore berth waiting times, arrival and departure delays, vessel counts, reported PSA berthing priorities and yard utilization come from the October 9, 2026 Kuehne+Nagel update and its seaexplorer data. Congestion ratings, berthing delay and waiting-vessel counts for Singapore, Tanjung Pelepas and Colombo come from the Tradlinx Port Congestion Index, Sep 22 – Oct 5, 2026 (data as of October 5). Missing-ETA figures come from a global Tradlinx analysis of 508,055 ocean container shipments with actual arrival confirmed by March 2026, and are not specific to Singapore’s current disruption. Berthing priorities, congestion conditions and sailing connections may change; confirm vessel schedules and cargo arrangements with the carrier before acting.
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.
Prefer email? Contact us directly at min.so@tradlinx.com (Americas), sondre.lyndon@tradlinx.com (Europe), or henry.jo@tradlinx.com (EMEA/Asia).
Leave a Reply