# An MSC shipment showed an extra stop at a port it never visited **URL:** \ **Category:** Known and fixed issues\ **Created:** [November 5, 2026, 8:26pm UTC](https://community.dockflow.com/t/an-msc-shipment-showed-an-extra-stop-at-a-port-it-never-visited/27 "2026-11-05T20:26:06Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![dockflow](https://community.dockflow.com/letter_avatar_proxy/v4/letter/d/a9a28c/32.png) [@dockflow](https://community.dockflow.com/u/dockflow)\ **Post date:** [November 5, 2026, 8:26pm UTC](https://community.dockflow.com/t/an-msc-shipment-showed-an-extra-stop-at-a-port-it-never-visited/27/1 "2026-11-05T20:26:07Z")
**Status:** Fixed since October 2026 **How to recognise it** An MSC shipment showed an unexpected stop at a specific port in a country where MSC had only named the country, for example India or Algeria. **Which shipments this affects** MSC shipments where MSC sent a location with a country but no city, such as India or Algeria. Locations with a named city were not affected. Matching such a location to a port could add a leg to the planned journey. **Cause** MSC sometimes sends a location as a country only, with the city left empty. **What changed** A location MSC gives as a country only is now shown as that country, never matched to a particular port. **Is past data corrected?** No. The fix applies to new events; earlier events keep their original wording. **How to check your shipment** Look at the route of the shipment. A location that MSC names only by country now shows as that country. If a port on a new route does not match your booking or MSC’s own tracking, send support the shipment reference. **Do you need to do anything?** Nothing. **Related** - [What if the data in Dockflow is wrong? | Dockflow Documentation](https://docs.dockflow.com/faqs/data-is-wrong) - [Why does Dockflow show something different from the carrier? | Dockflow Documentation](https://docs.dockflow.com/faqs/data-differs-from-carrier)