Zilliz

zilliz.com (opens in new tab)Status page (opens in new tab)

Status page says: Operational since Oct 19
Last 90 days: 1 incidents
Rewrites caught: None so far
Next deprecation: None announced

Zilliz incidents per day, last 90 days

Select a day to jump to its incidents below.

How Zilliz reports incidents

Not enough incidents to compare Zilliz with other vendors yet: a vendor needs 20 incidents in a year and 10 with full update detail (Zilliz has 2 and 4).

Provisional. Built nightly from every archived version of each incident, last on Oct 19. Compare all vendors

Dependencies

What Zilliz relies on and who relies on Zilliz, as observed in status-page incidents: who they blame, where they say they run, and who fails at the same time. Observed, not verified.

Zilliz depends on

Provider	Evidence	Signal
AWS	blamed in 1 incident; together in 1 outage event “…e fully recovered. 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.…” incident	Likely
Google Cloud	blamed in 1 incident; together in 1 outage event “…GCP outage impacting clusters in gcp-us-east4, gcp-us-central1, gcp-us-asia-southeast1 regions GCP experienced an outage which impacted our ability to access GCS object storage and GCR image repositor…” incident	Likely

Outage events: AWS us-east-1, Oct 20, 2025, Google Cloud, Jun 12, 2025.

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.