Vizion incident

Automatic carrier identification (ACI) disruption

Resolved on December 21, 2024.

resolved Jan 15, 2025, 06:38 PM UTC

Automatic carrier identification (ACI) references were not being processed beginning on December 21, 2024 through January 7, 2025 due to urgent maintenance of a carrier connection by the Engineering team. This disruption was not intended to persist across multiple days, and was resolved in the early afternoon (U.S. Pacific time) on January 7th. The Support team is working on reprocessing any references created during this timeframe in order to determine the supported carrier for the provided container ID and begin tracking the container if data is able to be found. We apologize for any inconvenience caused to users who make use of the ACI endpoint of the Vizion API. If there are any questions about this incident, please reach out to [email protected].

Started
Dec 21, 2024, 05:00 AM UTC
Resolved
Dec 21, 2024, 05:00 AM UTC
Duration
–
Detected by Pingoru
Dec 21, 2024, 05:00 AM UTC

Update timeline

  1. resolved Jan 15, 2025, 06:38 PM UTC

    Automatic carrier identification (ACI) references were not being processed beginning on December 21, 2024 through January 7, 2025 due to urgent maintenance of a carrier connection by the Engineering team. This disruption was not intended to persist across multiple days, and was resolved in the early afternoon (U.S. Pacific time) on January 7th. The Support team is working on reprocessing any references created during this timeframe in order to determine the supported carrier for the provided container ID and begin tracking the container if data is able to be found. We apologize for any inconvenience caused to users who make use of the ACI endpoint of the Vizion API. If there are any questions about this incident, please reach out to [email protected].

Your product runs on more than Vizion

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →