Port Congestion Map

Port Congestion Index

Compare rolling 30-day anchorage waits and berth dwell times from the cached congestion snapshot. The table shows the ten highest reported waits.

This feed provides rolling observations, not calendar-month editions or month-over-month trends. Cached data may be older during a provider outage.

Ports with reported waits

252

Median of port wait medians

0.37 days

Highest reported wait

6.34 days

Median of port berth medians

0.85 days

Top 10 reported anchorage waits

Ranked by each port's rolling 30-day median.

RankPortCodeCountryMedian waitMedian berth dwellAnchored vesselsTEU in 50 nmi areaLevel
1DurbanZADURZA6.34 days4.47 days5.58194,239.387High
2Khawr FakkanAEKLFAE4.62 days2.22 days22.54884,206.548High
3GebzeTRGEBTR4.29 days0.06 days19.871112,137.742High
4Subic BayPHSFSPH4.21 days0.84 days21.45243,992.258High
5Pointe NoireCGPNRCG3.79 days1.51 days8.93548,801.161High
6TemaGHTEMGH3.09 days1.34 days13.51698,251.387High
7NavegantesBRNVTBR2.99 days0.07 days4.87174,409.968High
8CotonouBJCOOBJ2.73 days0.71 days222,214.323High
9SoharOMSOHOM2.69 days1.03 days13.90359,393.387High
10PotiGEPTIGE2.21 days1.04 days2.3876,044.677High

Port congestion index FAQ

What period does this index cover?

Each port's anchorage and berth medians cover the upstream provider's rolling last 30 days. This is not a calendar-month report. Month-over-month comparisons are not available in this feed.

Where does the data come from?

The page uses the same cached backend congestion feed as Panvaya's live congestion map. The backend normally refreshes its snapshot every 12 hours and can serve an older snapshot during an upstream outage.

How are the summary cards calculated?

Reported ports are ranked by median anchorage wait in days. The summary cards give equal weight to each reported port's median; they are not vessel-weighted global averages. Missing values remain unavailable.

What do the vessel and TEU columns mean?

Anchored vessels uses the provider's vesselsAnchoredOutside field. TEU in the 50 nautical mile area uses teuInArea, which includes capacity in that area and is not a queued-container count. Areas can overlap, so their counts must not be summed as a unique global fleet.