Status: Fixed since June 2026
How to recognise it
A shipment on a Red Sea route could show a location in Antarctica, or a time that made no sense for the port, where you expected Aqaba in Jordan. The carrier’s own page showed the right port, so the difference looked like a mistake in the tracking.
Which shipments this affects
Shipments where a carrier sends the word AQABA as the location code, on routes that call at the port of Aqaba in Jordan.
Cause
AQABA is also a valid UN/LOCODE. Read as a code, AQ is the country code of Antarctica and ABA is a research station there. Carriers, Hapag-Lloyd among them, send the same word to mean the port of Aqaba.
What changed
Dockflow now reads AQABA as Aqaba in Jordan, with the code JOAQJ and the local time of that port.
Is past data corrected?
No. The fix applies from that month on; earlier data stays as it was.
How to check your shipment
Open the shipment and check that the location reads Aqaba, Jordan, and that its times fit that port. If it still shows another place, contact support with the reference.
Do you need to do anything?
Nothing.