Durban Gateway Terminal backlog follows terminal operating system cutover
Durban Gateway Terminal backlog follows terminal operating system cutover. The disruption ran from 2026-08-15 (15 August 2026), and is ongoing, affecting Durban. Durban averaged 6.3 calls per day during the event window against an expected 6.7 (-6.7%). Durban averaged 1.6 calls per day during the event window against an expected 1.8 (-0.2).
Key facts
- Started
- 2026-08-15 (15 August 2026)
- Ended
- Not ended
- Status
- ongoing
- Severity
- 2 Moderate
- Scope
- terminal
- Chokepoints
- None
- Ports
- Durban
- Lanes
- None
- Countries
- South Africa
- Confidence
- medium: The cutover date and the terminal's own notice are relayed by an industry association, and the throughput and waiting figures come from trade press without a direct terminal statement; the effect in port call counts is small and the backlog is still open.
- First reported
- 2026-08-11 (11 August 2026)
- 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.
What happened
Durban Gateway Terminal, a container terminal at Durban, South Africa, began working through a growing backlog after it switched to the Navis N4 terminal operating system on 2026-08-15 (15 August 2026). The operator had told users that vessel and landside work would pause for about twelve hours during the cutover and that some delays would follow. Reports from the following two weeks describe queues of trucks waiting up to about 30 hours, ships waiting longer at anchorage, refrigerated export containers spoiling in queues, and a temporary pause on accepting reefer boxes. The operator said the system was stable by 2026-08-27 but that equipment constraints and yard congestion meant a return to normal would take time.
Measured effect
Port calls, Durban
- Baseline (expected)
- 6.7 calls per day
- Observed
- 6.3 calls per day
- Change
- -0.5 (-6.7%)
- Standardised score
- -0.2
- Event window
- 2026-08-15 to 2026-11-06 (84 days, provisional)
- Baseline window
- 2026-06-13 to 2026-08-07 (56 valid days)
- Method
- wfm-effect-1.0
- Computed
- 2026-11-10 (10 November 2026), data revision 2:481108da4c58
Source: IMF PortWatch (portwatch.imf.org), International Monetary Fund, using UN Global Platform AIS data. Statistics derived by World Freight Monitor. Terms. Retrieved 2026-11-10 (10 November 2026).
| Date | calls per day |
|---|---|
| 2026-06-06 | 6 |
| 2026-06-07 | 8 |
| 2026-06-08 | 6 |
| 2026-06-09 | 8 |
| 2026-06-10 | 7 |
| 2026-06-11 | 6 |
| 2026-06-12 | 3 |
| 2026-06-13 | 9 |
| 2026-06-14 | 4 |
| 2026-06-15 | 4 |
| 2026-06-16 | 9 |
| 2026-06-17 | 10 |
| 2026-06-18 | 11 |
| 2026-06-19 | 9 |
| 2026-06-20 | 4 |
| 2026-06-21 | 5 |
| 2026-06-22 | 10 |
| 2026-06-23 | 11 |
| 2026-06-24 | 7 |
| 2026-06-25 | 6 |
| 2026-06-26 | 7 |
| 2026-06-27 | 7 |
| 2026-06-28 | 4 |
| 2026-06-29 | 11 |
| 2026-06-30 | 5 |
| 2026-07-01 | 5 |
| 2026-07-02 | 7 |
| 2026-07-03 | 5 |
| 2026-07-04 | 5 |
| 2026-07-05 | 8 |
| 2026-07-06 | 6 |
| 2026-07-07 | 7 |
| 2026-07-08 | 10 |
| 2026-07-09 | 5 |
| 2026-07-10 | 4 |
| 2026-07-11 | 7 |
| 2026-07-12 | 3 |
| 2026-07-13 | 6 |
| 2026-07-14 | 6 |
| 2026-07-15 | 8 |
| 2026-07-16 | 10 |
| 2026-07-17 | 6 |
| 2026-07-18 | 8 |
| 2026-07-19 | 6 |
| 2026-07-20 | 10 |
| 2026-07-21 | 7 |
| 2026-07-22 | 4 |
| 2026-07-23 | 7 |
| 2026-07-24 | 0 |
| 2026-07-25 | 10 |
| 2026-07-26 | 5 |
| 2026-07-27 | 7 |
| 2026-07-28 | 7 |
| 2026-07-29 | 8 |
| 2026-07-30 | 2 |
| 2026-07-31 | 4 |
| 2026-08-01 | 7 |
| 2026-08-02 | 3 |
| 2026-08-03 | 9 |
| 2026-08-04 | 7 |
| 2026-08-05 | 8 |
| 2026-08-06 | 8 |
| 2026-08-07 | 8 |
| 2026-08-08 | 2 |
| 2026-08-09 | 9 |
| 2026-08-10 | 0 |
| 2026-08-11 | 7 |
| 2026-08-12 | 7 |
| 2026-08-13 | 8 |
| 2026-08-14 | 8 |
| 2026-08-15 | 10 |
| 2026-08-16 | 7 |
| 2026-08-17 | 6 |
| 2026-08-18 | 2 |
| 2026-08-19 | 6 |
| 2026-08-20 | 4 |
| 2026-08-21 | 6 |
| 2026-08-22 | 5 |
| 2026-08-23 | 8 |
| 2026-08-24 | 5 |
| 2026-08-25 | 4 |
| 2026-08-26 | 10 |
| 2026-08-27 | 0 |
| 2026-08-28 | 5 |
| 2026-08-29 | 0 |
| 2026-08-30 | 9 |
| 2026-08-31 | 18 |
| 2026-09-01 | 2 |
| 2026-09-02 | 8 |
| 2026-09-03 | 3 |
| 2026-09-04 | 4 |
| 2026-09-05 | 9 |
| 2026-09-06 | 7 |
| 2026-09-07 | 5 |
| 2026-09-08 | 3 |
| 2026-09-09 | 4 |
| 2026-09-10 | 6 |
| 2026-09-11 | 6 |
| 2026-09-12 | 4 |
| 2026-09-13 | 10 |
| 2026-09-14 | 0 |
| 2026-09-15 | 7 |
| 2026-09-16 | 5 |
| 2026-09-17 | 3 |
| 2026-09-18 | 2 |
| 2026-09-19 | 11 |
| 2026-09-20 | 7 |
| 2026-09-21 | 7 |
| 2026-09-22 | 5 |
| 2026-09-23 | 5 |
| 2026-09-24 | 5 |
| 2026-09-25 | 7 |
| 2026-09-26 | 5 |
| 2026-09-27 | 6 |
| 2026-09-28 | 5 |
| 2026-09-29 | 6 |
| 2026-09-30 | 9 |
| 2026-10-01 | 7 |
| 2026-10-02 | 10 |
| 2026-10-03 | 5 |
| 2026-10-04 | 3 |
| 2026-10-05 | 7 |
| 2026-10-06 | 4 |
| 2026-10-07 | 5 |
| 2026-10-08 | 9 |
| 2026-10-09 | 6 |
| 2026-10-10 | 6 |
| 2026-10-11 | 5 |
| 2026-10-12 | 7 |
| 2026-10-13 | 7 |
| 2026-10-14 | 8 |
| 2026-10-15 | 8 |
| 2026-10-16 | 9 |
| 2026-10-17 | 7 |
| 2026-10-18 | 6 |
| 2026-10-19 | 5 |
| 2026-10-20 | 8 |
| 2026-10-21 | 8 |
| 2026-10-22 | 6 |
| 2026-10-23 | 6 |
| 2026-10-24 | 4 |
| 2026-10-25 | 9 |
| 2026-10-26 | 13 |
| 2026-10-27 | 5 |
| 2026-10-28 | 4 |
| 2026-10-29 | 8 |
| 2026-10-30 | 5 |
| 2026-10-31 | 14 |
| 2026-11-01 | 5 |
| 2026-11-02 | 9 |
| 2026-11-03 | 8 |
| 2026-11-04 | 5 |
| 2026-11-05 | 4 |
| 2026-11-06 | 10 |
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.
Container ship port calls, Durban
- Baseline (expected)
- 1.8 calls per day
- Observed
- 1.6 calls per day
- Change
- -0.2 (percent omitted, baseline too small)
- Standardised score
- -0.1
- Event window
- 2026-08-15 to 2026-11-06 (84 days, provisional)
- Baseline window
- 2026-06-13 to 2026-08-07 (56 valid days)
- Method
- wfm-effect-1.0
- Computed
- 2026-11-10 (10 November 2026), data revision 2:e32253f162d7
Source: IMF PortWatch (portwatch.imf.org), International Monetary Fund, using UN Global Platform AIS data. Statistics derived by World Freight Monitor. Terms. Retrieved 2026-11-10 (10 November 2026).
| Date | calls per day |
|---|---|
| 2026-06-06 | 3 |
| 2026-06-07 | 0 |
| 2026-06-08 | 2 |
| 2026-06-09 | 4 |
| 2026-06-10 | 1 |
| 2026-06-11 | 1 |
| 2026-06-12 | 1 |
| 2026-06-13 | 3 |
| 2026-06-14 | 1 |
| 2026-06-15 | 1 |
| 2026-06-16 | 6 |
| 2026-06-17 | 2 |
| 2026-06-18 | 1 |
| 2026-06-19 | 1 |
| 2026-06-20 | 3 |
| 2026-06-21 | 2 |
| 2026-06-22 | 2 |
| 2026-06-23 | 2 |
| 2026-06-24 | 2 |
| 2026-06-25 | 3 |
| 2026-06-26 | 2 |
| 2026-06-27 | 2 |
| 2026-06-28 | 1 |
| 2026-06-29 | 3 |
| 2026-06-30 | 2 |
| 2026-07-01 | 2 |
| 2026-07-02 | 1 |
| 2026-07-03 | 2 |
| 2026-07-04 | 2 |
| 2026-07-05 | 0 |
| 2026-07-06 | 2 |
| 2026-07-07 | 2 |
| 2026-07-08 | 3 |
| 2026-07-09 | 2 |
| 2026-07-10 | 1 |
| 2026-07-11 | 1 |
| 2026-07-12 | 0 |
| 2026-07-13 | 2 |
| 2026-07-14 | 3 |
| 2026-07-15 | 1 |
| 2026-07-16 | 2 |
| 2026-07-17 | 3 |
| 2026-07-18 | 0 |
| 2026-07-19 | 1 |
| 2026-07-20 | 3 |
| 2026-07-21 | 2 |
| 2026-07-22 | 1 |
| 2026-07-23 | 4 |
| 2026-07-24 | 0 |
| 2026-07-25 | 3 |
| 2026-07-26 | 1 |
| 2026-07-27 | 1 |
| 2026-07-28 | 3 |
| 2026-07-29 | 4 |
| 2026-07-30 | 0 |
| 2026-07-31 | 1 |
| 2026-08-01 | 2 |
| 2026-08-02 | 0 |
| 2026-08-03 | 3 |
| 2026-08-04 | 3 |
| 2026-08-05 | 1 |
| 2026-08-06 | 3 |
| 2026-08-07 | 1 |
| 2026-08-08 | 1 |
| 2026-08-09 | 3 |
| 2026-08-10 | 0 |
| 2026-08-11 | 1 |
| 2026-08-12 | 3 |
| 2026-08-13 | 0 |
| 2026-08-14 | 4 |
| 2026-08-15 | 2 |
| 2026-08-16 | 2 |
| 2026-08-17 | 1 |
| 2026-08-18 | 0 |
| 2026-08-19 | 1 |
| 2026-08-20 | 1 |
| 2026-08-21 | 1 |
| 2026-08-22 | 2 |
| 2026-08-23 | 3 |
| 2026-08-24 | 1 |
| 2026-08-25 | 1 |
| 2026-08-26 | 4 |
| 2026-08-27 | 0 |
| 2026-08-28 | 0 |
| 2026-08-29 | 0 |
| 2026-08-30 | 4 |
| 2026-08-31 | 4 |
| 2026-09-01 | 0 |
| 2026-09-02 | 1 |
| 2026-09-03 | 0 |
| 2026-09-04 | 0 |
| 2026-09-05 | 4 |
| 2026-09-06 | 1 |
| 2026-09-07 | 3 |
| 2026-09-08 | 1 |
| 2026-09-09 | 1 |
| 2026-09-10 | 0 |
| 2026-09-11 | 2 |
| 2026-09-12 | 2 |
| 2026-09-13 | 1 |
| 2026-09-14 | 0 |
| 2026-09-15 | 2 |
| 2026-09-16 | 3 |
| 2026-09-17 | 0 |
| 2026-09-18 | 1 |
| 2026-09-19 | 1 |
| 2026-09-20 | 2 |
| 2026-09-21 | 1 |
| 2026-09-22 | 1 |
| 2026-09-23 | 2 |
| 2026-09-24 | 1 |
| 2026-09-25 | 1 |
| 2026-09-26 | 3 |
| 2026-09-27 | 2 |
| 2026-09-28 | 0 |
| 2026-09-29 | 3 |
| 2026-09-30 | 1 |
| 2026-10-01 | 3 |
| 2026-10-02 | 4 |
| 2026-10-03 | 0 |
| 2026-10-04 | 3 |
| 2026-10-05 | 1 |
| 2026-10-06 | 0 |
| 2026-10-07 | 1 |
| 2026-10-08 | 2 |
| 2026-10-09 | 4 |
| 2026-10-10 | 1 |
| 2026-10-11 | 2 |
| 2026-10-12 | 3 |
| 2026-10-13 | 0 |
| 2026-10-14 | 2 |
| 2026-10-15 | 3 |
| 2026-10-16 | 1 |
| 2026-10-17 | 2 |
| 2026-10-18 | 1 |
| 2026-10-19 | 1 |
| 2026-10-20 | 2 |
| 2026-10-21 | 1 |
| 2026-10-22 | 4 |
| 2026-10-23 | 0 |
| 2026-10-24 | 1 |
| 2026-10-25 | 3 |
| 2026-10-26 | 3 |
| 2026-10-27 | 1 |
| 2026-10-28 | 2 |
| 2026-10-29 | 2 |
| 2026-10-30 | 2 |
| 2026-10-31 | 3 |
| 2026-11-01 | 1 |
| 2026-11-02 | 2 |
| 2026-11-03 | 3 |
| 2026-11-04 | 1 |
| 2026-11-05 | 0 |
| 2026-11-06 | 3 |
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.
Previous computations (24)
- 2026-09-29, wfm-effect-1.0, revision 1:318fbfa8b3a7: observed 2.1 against baseline 1.8 calls per day
- 2026-09-22, wfm-effect-1.0, revision 1:25a7e3cda9e5: observed 2.1 against baseline 1.8 calls per day
- 2026-10-18, wfm-effect-1.0, revision 1:cc98a1bd4151: observed 7.7 against baseline 7.5 calls per day
- 2026-10-06, wfm-effect-1.0, revision 1:138f03d035e4: observed 7.6 against baseline 7.5 calls per day
- 2026-09-22, wfm-effect-1.0, revision 1:ce5558042f18: observed 7.8 against baseline 7.5 calls per day
- 2026-10-18, wfm-effect-1.0, revision 1:4a26a9b52102: observed 2.0 against baseline 1.8 calls per day
- 2026-10-21, wfm-effect-1.0, revision 1:21cf952f6444: observed 2.1 against baseline 1.8 calls per day
- 2026-10-21, wfm-effect-1.0, revision 1:4f5b41557416: observed 7.6 against baseline 7.5 calls per day
- 2026-09-20, wfm-effect-1.0, revision 1:423360432d76: observed 2.0 against baseline 1.8 calls per day
- 2026-09-29, wfm-effect-1.0, revision 1:0004091e1d36: observed 7.8 against baseline 7.5 calls per day
- 2026-09-20, wfm-effect-1.0, revision 1:5b6ddb8fe173: observed 7.8 against baseline 7.5 calls per day
- 2026-10-06, wfm-effect-1.0, revision 1:451f8d4425c3: observed 2.1 against baseline 1.8 calls per day
- 2026-10-18, wfm-effect-1.0, revision 2:45923860b8bb: observed 1.5 against baseline 1.8 calls per day
- 2026-10-21, wfm-effect-1.0, revision 2:c8c5a1a373a7: observed 6.0 against baseline 6.7 calls per day
- 2026-10-21, wfm-effect-1.0, revision 2:00913038a1eb: observed 1.5 against baseline 1.8 calls per day
- 2026-09-20, wfm-effect-1.0, revision 1:4f624d3b25ab: observed 5.8 against baseline 6.7 calls per day
- 2026-09-20, wfm-effect-1.0, revision 1:65be50743a35: observed 1.4 against baseline 1.7 calls per day
- 2026-09-22, wfm-effect-1.0, revision 2:1fc9960d2ad9: observed 5.5 against baseline 6.7 calls per day
- 2026-09-22, wfm-effect-1.0, revision 2:6e66e4a0309a: observed 1.4 against baseline 1.8 calls per day
- 2026-09-29, wfm-effect-1.0, revision 2:ede93d413784: observed 5.7 against baseline 6.7 calls per day
- 2026-09-29, wfm-effect-1.0, revision 2:444713aa854e: observed 1.4 against baseline 1.8 calls per day
- 2026-10-06, wfm-effect-1.0, revision 2:39ad244c4c70: observed 5.9 against baseline 6.7 calls per day
- 2026-10-06, wfm-effect-1.0, revision 2:88eab560b937: observed 1.5 against baseline 1.8 calls per day
- 2026-10-18, wfm-effect-1.0, revision 2:a2fb07127ce4: observed 5.8 against baseline 6.7 calls per day
Replay
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.
Timeline
- A 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. [s3]
- The terminal goes live on Navis N4; users must register afresh for access. [s1] [s3]
- Reports 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. [s1] [s2]
Cause
Corrections
No corrections to this record as of 2026-09-20 (20 September 2026).
Sources
- [s1] WorldCargo News, NAVIS N4 rollout leaves Durban Gateway fighting operational backlog, published 2026-08-27 (27 August 2026), accessed 2026-09-20. Archived copy. (press)
- [s2] Agri News, System Migration Triggers Major Backlog at Durban Gateway Terminal, published 2026-08-27 (27 August 2026), accessed 2026-09-20. Archived copy. (press)
- [s3] Southern African Association of Freight Forwarders, DGT Navis N4 Go-Live Update, published 2026-08-11 (11 August 2026), accessed 2026-09-20. Archived copy. (press)
Cite this record
The address of this record is permanent and a correction is always logged on this page, so a citation names the version you read. Add the date you accessed it.
Plain text
World Freight Monitor. "Durban Gateway Terminal backlog follows terminal operating system cutover." Last updated 2026-09-20 (20 September 2026). https://worldfreightmonitor.com/events/2026/durban-gateway-terminal-navis-backlog-2026/
APA
World Freight Monitor. (2026). Durban Gateway Terminal backlog follows terminal operating system cutover. World Freight Monitor. https://worldfreightmonitor.com/events/2026/durban-gateway-terminal-navis-backlog-2026/
BibTeX
@misc{wfm_durban_gateway_terminal_navis_backlog_2026,
author = {{World Freight Monitor}},
title = {Durban Gateway Terminal backlog follows terminal operating system cutover},
year = {2026},
note = {Last updated 2026-09-20},
url = {https://worldfreightmonitor.com/events/2026/durban-gateway-terminal-navis-backlog-2026/}
}