Zilliz

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.

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 was introduced by a backend service update and was fully resolved by rolling that change back.

Our systems have fully recovered.

We are continuing to monitor for any further issues.

We are seeing recovery for affected instances in the region. We will continue to monitor the situation and provider further updates as necessary.

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 mitigate the problem. We will provide another update as soon as more information is available.

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 and edit operations were also impacted in those regions. As of now, GCP services have fully recovered, and our services have fully recovered as well.

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 systems continued operating normally.