Vizion had 39 outages in the last 2 years totaling 4050h 58m of downtime — averaging 1.6 incidents per month.
There were 39 Vizion outages since July 8, 2024 totaling 4050h 58m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
A fix has been implemented and connection to the carrier has been restored.
MSC is fully operational as of Friday Jun 26th.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A disruption was identified with OOCL (Orient Overseas Container Line) where newly-created references were not being processed. A hotfix was released on 4/22/2026, and all new and existing OOCL references are being processed through the queue as expected.
Connectivity to Maersk is degraded and our Engineering teams are currently investigating the cause. We will update this incident as soon as more information is available. Vizion references may still be created for Maersk shipments during this time and they will be processed for updates once connectivity has been restored.
Fix has been identified and implemented. Processing for Maersk references is back to normal.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
The connection has been partially restored and will continue to improve as additional strategies are implemented.
This incident has been resolved.
Current status: Our third-party cloud platform has identified network connectivity issues and isolated their source. They are implementing mitigations, and we are continuing to monitor recovery progress. Customer experience: Customers may be unable to access or use multiple core Tradeview services and features. Affected users may be unable to successfully load pages, query via data explorer, or utilize data visualizations. ETA: While an exact ETA is not yet available, we'll provide an exact timeline as soon as possible. Incident start time: 07:20 UTC October 20, 2025
Current status: Our third-party cloud platform is continuing mitigation efforts and are reporting improvements. We are continuing to monitor recovery progress. Customer experience: Customers may be unable to access or use multiple core Tradeview services and features. Affected users may be unable to successfully load pages, query via data explorer, or utilize data visualizations. ETA: While an exact ETA is not yet available, we'll provide an exact timeline as soon as possible.
Current status: While our third-party cloud platform continues to monitor their service health following their mitigation actions, we have observed that the Tradeview service health has recovered as of 6:08pm PST. We're continuing to monitor to ensure our service remains healthy. Customer experience: Some users may experience fewer issues utilizing Tradeview services and features. Affected users may be unable to successfully load pages, query via data explorer, or utilize data visualizations. Preliminary root cause: A third-party cloud platform experienced networking issues, which caused access problems to Tradeview services.
Current status: Our third-party cloud platform has identified network connectivity issues and isolated their source. They are implementing mitigations, and we are continuing to monitor recovery progress. Customer experience: Customers may be unable to access or use multiple core Tradeview services and features. Affected users may be unable to successfully load pages, query via data explorer, or utilize data visualizations. Incident start time: 07:20 UTC October 20, 2025 Preliminary root cause: A third-party cloud platform experienced networking issues, which were traced to the failure of an underlying internal subsystem responsible for monitoring the health of its network load balancers. This ultimately caused access issues for Tradeview services and features.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
A subset of references for the carriers CMA (CMDU), Hapag-Lloyd (HLCU), Maersk (MAEU), and MSC (MSCU) were identified as being stalled and not being correctly processed in order to generate new tracking updates. A hotfix has been implemented as of 2025-07-30, and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are aware of an issue causing the Container Trace endpoint to return 500 errors. Our engineering team has identified the root cause and is actively working on a fix. We’ll share updates as soon as more information is available.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
References created using the API's Automatic Carrier Identification, or ACI, endpoint were being successfully created but not being processed to identify the supported carrier and track the container movements if supported after the latest API release on May 8th. The Engineering team was able to resolve an error related to ACI processing which caused the prolonged delays in processing those references. The hotfix was deployed before the end of the day on May 13th.
Connectivity to BNSF is degraded and our team is investigating the cause. We will update this incident as soon as more information is available.
This incident has been resolved.