August 28, 2026 - September 11, 2026
about 1 hour ago
Container Tracking API
New features
- Expanded carrier coverage: tracking support for Vanguard Logistics, SACO Shipping, Independent Container Line, and ECU Worldwide is now enabled for all customers.
- MSC: added a container-only fallback so booking-plus-container references still return data when a master bill of lading lookup fails.
- Booking-number tracking is now supported for Atlantic Container Line.
Bugs squashed
- Fixed a systematic late bias in Vizion-sourced Port of Discharge arrival estimates, which could run several days late without converging.
- Fixed Maersk laden gate-in and gate-out events that could lose their empty/laden indicator, causing laden filters to miss a large volume of events.
- Fixed OOCL ETAs where ambiguous timezone abbreviations could be parsed to the wrong UTC offset.
- Fixed an OOCL issue where the destination port could be misresolved on the first reference update, with a transshipment hub or the origin selected as the destination.
- OOCL vessel milestones now include the vessel name and IMO number, backfilled where they were missing.
- Fixed Sea-Lead references that could accumulate vessel position milestones indefinitely after the container journey ended.
- Fixed SITC shipments where a recovered Port of Discharge gate-out could be missing its laden indicator.
- Fixed Wan Hai journey stitching that could concatenate two consecutive journeys into a single reference.
- Fixed booking and bill-of-lading lookups that could select the wrong carrier and then return no data.
- Fixed an issue where a Last Known Position could return a stale position compared with Container Trace.
- Future-dated actual transport and equipment events are now suppressed.
- Cargo cutoff date and Terminal ERD are no longer emitted as journey tracking events.
- Fixed an issue where estimated-arrival-changed events could be dropped during multi-hour windows.