
Zonos Incident History
Operational
checked Aug 26, 2026 4:40 AM UTC · Zonos's official status page
Zonos is up and running.
Zonos is currently operational with all systems functioning normally.
Incident History
Showing incidents from the last 15 days
Report: "2026-03-11 - Elevated Error Rates on Inference Services"
Last update**What products were affected and what was the impact?** Classify, Country of Origin Impact: DEGRADED PERFORMANCE **What timeframe did this issue occur?** | **Date** | **Time** | | --- | --- | | Mar 11, 2026 | 2026-03-11 10:12 - 2026-03-11 12:06 | **How was the issue detected?** Zonos observed elevated error rates affecting Classify and Country of Origin APIs. **What functionality was affected?** A portion of Classify and Country of Origin inference requests did not return a valid response. **What was the root cause?** A firmware issue on a subset of GPU nodes caused network connectivity failures. This caused the nodes to enter an unhealthy state. Our reconnect logic did not properly remove unhealthy nodes from the pool, so they continued to receive requests. **What was the resolution of the problem, and what steps are being taken to prevent future issues?** Shortly after discovering the issue, we restarted nodes to resolve the connectivity issues and restore service. We then identified the reconnect logic issue, and released a fix to prevent future issues. We have scheduled a firmware upgrade on all nodes to resolve the underlying network issue. We have also refined our alerting to catch errors more quickly in the future.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
Report: "2026-08-03 Elevated error rates for landed cost quotes"
Last updateThis incident has been resolved.
We are continuing to monitor for any further issues.
A fix has been implemented and we are monitoring the results.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.