Status: Fixed since May 2026
How to recognise it
You could see an ATA that was too early and pointed to a transshipment port. The API could show an older, wrong ETA while the portal showed the correct ETA. This happened when a route called at the same port twice.
Which shipments this affects
This affected shipments on routes that called at the same port twice.
Cause
Carrier data listed a port, then another port, then the first port again.
What changed
The repeat visit is no longer classified as the final port of discharge with its own final arrival. The final arrival and ATA point to the correct final port. The API and portal show the same ETA.
Is past data corrected?
Nothing to correct: the change affects how new data is read.
How to check your shipment
Open the shipment and compare the final arrival port and ATA with the route. Check that the API ETA matches the portal ETA. Contact support if the final arrival still points to a transshipment port or the two ETAs differ.
Do you need to do anything?
Nothing.