Zilliz Outage History

Zilliz is up right now

Zilliz had 2 outages in the last 2 years totaling 1h 52m of downtime — averaging 0.1 incidents per month.

There were 2 Zilliz outages since June 13, 2025 totaling 1h 52m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.zilliz.com/uptime

Major October 20, 2025

Service disruption

Detected by Pingoru
Oct 20, 2025, 08:54 AM UTC
Resolved
Oct 20, 2025, 10:47 AM UTC
Duration
1h 52m
Affected: us-east-1
Timeline · 4 updates
  1. identified Oct 20, 2025, 08:54 AM UTC

    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.

  2. monitoring Oct 20, 2025, 09:47 AM UTC

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

  3. monitoring Oct 20, 2025, 10:05 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Oct 20, 2025, 10:47 AM UTC

    Our systems have fully recovered.

Read the full incident report →

Major June 13, 2025

GCP outage impacting clusters in gcp-us-east4, gcp-us-central1, gcp-us-asia-southeast1 regions

Detected by Pingoru
Jun 13, 2025, 06:11 AM UTC
Resolved
Jun 12, 2025, 08:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Jun 13, 2025, 06:11 AM UTC

    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.

Read the full incident report →