- General: Hotfix to resolve ACI reference processing issue, and temporarily remove PIL from ACI carrier check
- COSCO: Track by booking support
- Allow Container Trace endpoint to be used with simple tracking
- New SeaLead supported carrier
- Maersk: Improve inland destination logic
- Add section to API reference for Vizion open API spec
- CMA: Carrier returns "unknown" as vessel IMO in some payloads
- Evergreen: Handle "-SMART" suffix added with track by booking number
- OOCL: Resolve high rate of extraction failures
- USCHS: Terminal event standardizations
- SNKO: Standardized event mapping
- HHLA: Terminal events parsing improvements
- CAMTR: Increase terminal event coverage
- Evergreen: Resolve high track by booking failure rates
- USCHS: Terminal event standardizations
- General: Duplicate prevention now ignores the
callback_url property; unique URLs cannot be used to create a duplicate reference
- General: Add unique milestone IDs and versions to milestone objects within reference updates
- Heung-A: Resolve connection outage
- PIL: Resolve connection outage
- Hapag-Lloyd: Better standardization for transshipment events within HLCU references (including RTP journey codes related to DCSA)
- Hapag-Lloyd: Map combined rail events to standardized rail milestones
- Yang Ming: Event standardizations
- General: Integrate with HHLA terminal schedules
- CAMTR: Increase terminal coverage
- USCHS: Address failiures due to large payloads
- USCHS: Event standardizations
- Maersk: vessel identification improvements
- Arkas: High rate of extraction failures
- Pacific International Line: High rate of extraction failures
- ZIM: event standardizations
- Hyundai: location mappings
- Increase coverage at CAMTR
- CMA: Container still in active shipment status randomly returning "no_data"
- TS Line: Incorrect timestamp at POL
- ONE Line: Different POD events can be standardized into similar or duplicated milestones in the update payload
- ONE Line: Wrong description at transshipment port
- MSC: Improved inland destination logic related to destination port override
- USCHS: event standardizations
- Arkas: event standardizations
- Improve Maersk vessel identification
- General location data enhancements
- PIL: extraction failures
- SITC: extraction failures
- Crowley: extraction failures
- USCHS event standardizations
- Hyundai: High failure rates when subscribing by container ID and carrier code
- Terminal event descriptions do not match documented standardization
- Evergreen: high rate of extraction failures
- ONE Line: POD is a transshipment port and not the final POD
- SITC: Wrong description at origin port; incorrectly treated as a transshipment location
- CK Line: Fix incorrect descriptions
- MSC: high rate of extraction failures
- Wan Hai: Track by booking support
- Maersk: Update inland origin detection logic
- MSC: Carrier sourced destination arrival milestones not de-duplicated
- ONE Line: Investigate high failure rates
- CMA: Investigate high failure rates
- OOCL high failure rates fix
- Wan Hai: Missing vessel departure and arrivals for empty return containers
- SITC: Wrong description at origin port; incorrectly treated as a transshipment location
- Maersk: Same location returned for Inland Origin and Origin Port
- PIL: high rate of extraction failures
- Wan Hai: Uptick in extraction failures and no data statuses for valid BL lookups
- Yang Ming: Extraction method improvements
- Yang Ming: Track by booking support
- Auto Carrier Identification reference carrier code mismatch
- Maersk: "Gate in empty return" available in raw data but not included in update payload
- Duplicate "Departure from Origin Milestones"
- Cosco: Lack of Discharge at Destination
- ONE Line: Investigate high rate of "no_data" statuses
