Zilliz
Infrastructure. Source: Zilliz status page.
- Incidents, last 90 days
- 0
- Median to mitigation
- none resolved
- Median to resolution
- none resolved
- p95 to resolution
- none resolved
- Naming an upstream provider
- no incidents
- With a postmortem on the status page
- no incidents
Incidents per month
All recorded incidents
Elevated errors on control plane API (July 22)
Affected: REST API / OpenAPI
Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Between 09:00 and 10:07 UTC on July 22, 2026, a subset of Zilliz Cloud control plane API requests returned authorization errors. Monitoring and metrics endpoints were the most affected. Running clusters, data access, and query traffic were not affected at any point. The issue...
-
resolved
This incident was fully resolved at 10:07 UTC on July 22, 2026. Control plane API requests have been operating normally since. Running clusters, data access, and query traffic were not affected at any point.
Excerpts are shortened. Read the full incident on Zilliz's status page.
Service disruption
Affected: us-east-1 (Virginia)
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: AWS.
-
identified
Starting at approximately 07:31 UTC October 20, 2025, customers in the AWS us-east-1 region may experience failures in normal cluster operations as well as accessing their clusters. We have identified the issue as an outage in AWS services and are actively working with them to...
-
monitoring
We are seeing recovery for affected instances in the region. We will continue to monitor the situation and provider further updates as necessary.
-
monitoring
We are continuing to monitor for any further issues.
-
resolved
Our systems have fully recovered.
Excerpts are shortened. Read the full incident on Zilliz's status page.
GCP outage impacting clusters in gcp-us-east4, gcp-us-central1, gcp-us-asia-southeast1 regions
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: Google Cloud.
-
resolved
GCP experienced an outage which impacted our ability to access GCS object storage and GCR image repository services. This resulted in some Zilliz Cloud clusters to be unavailable in the GCP regions of gcp-us-east4, gcp-us-central1, and gcp-us-asia-southeast1. Cluster creation...
Excerpts are shortened. Read the full incident on Zilliz's status page.
Private Link Connection Issues
Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
resolved
The incident has been resolved. Due to an an incident, from 8:30 to 10:36 UTC some users were unable to connect to their clusters over private links. We estimate this affected around less than 5% of our users. Once we detected the problem, we were able to resolve it and our...
Excerpts are shortened. Read the full incident on Zilliz's status page.