Durban Gateway Terminal backlog follows terminal operating system cutover

Day

30 (as of 2026-09-13 (13 September 2026))

Started

2026-08-15 (15 August 2026)

Severity

2 Moderate

Chokepoints

None

Ports

Durban

Lanes

None

• Severity basis: Terminal disruption lasting over 72 hours at a major container terminal; portwatch-port-calls for Durban averaged about 5 calls a week from 2026-08-17 against about 6.7 in June and July.

Expected before the event

6.7 calls per day

Last 7 days

5.7

Last 28 days

5.8 (-14%)

Average since the start

5.8

This is a measured change in public data during the event window, compared with a baseline before it. It shows timing, not cause. We describe an event as causing a change only when an official source says so.

Expected before the event

1.8 calls per day

Last 7 days

1.7

Last 28 days

1.4 (-22%)

Average since the start

1.4

This is a measured change in public data during the event window, compared with a baseline before it. It shows timing, not cause. We describe an event as causing a change only when an official source says so.

1. 2026-08-27Reports describe truck queues of up to about 30 hours, longer vessel stays and spoiled refrigerated cargo. The terminal pauses acceptance of reefer boxes, says the system is stable, and says equipment limits and the backlog mean normal flow will take time.
2. 2026-08-15The terminal goes live on Navis N4; users must register afresh for access.
3. 2026-08-11A freight forwarders association relays the terminal's notice of a cutover to the new operating system, starting 18:00 on 15 August, with no vessel or landside operations for about twelve hours.

Full record with sources, cause and measured effect. All ongoing disruptions.