outages.live
Live

Zilliz

Zilliz is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

0

Days with an incident

0

Median duration

No data

Longest incident

No data

Components

28

AWS

us-west-2 (Oregon) Operational
90 days agoNo incidentsToday
us-east-2 (Ohio) Operational
90 days agoNo incidentsToday
ap-southeast-1 (Singapore) Operational
90 days agoNo incidentsToday
us-east-1 (Virginia) Operational
90 days agoNo incidentsToday
eu-central-1 (Frankfurt) Operational
90 days agoNo incidentsToday
ap-northeast-1 (Tokyo) Operational
90 days agoNo incidentsToday
ca-central-1 (Canada Central) Operational
90 days agoNo incidentsToday
ap-southeast-2 (Sydney) Operational
90 days agoNo incidentsToday
eu-west-1 (Ireland) Operational
90 days agoNo incidentsToday
ap-northeast-2 (Seoul) Operational
90 days agoNo incidentsToday
eu-west-2 ( London ) Operational
90 days agoNo incidentsToday

Control Plane

Console / Dashboard Operational
90 days agoNo incidentsToday
REST API / OpenAPI Operational
90 days agoNo incidentsToday
User & Auth Operational
90 days agoNo incidentsToday
Billing Operational
90 days agoNo incidentsToday

GCP

us-west-1 (Oregon) Operational
90 days agoNo incidentsToday
asia-southeast1 (Singapore) Operational
90 days agoNo incidentsToday
us-east4 (N.Virginia) Operational
90 days agoNo incidentsToday
europe-west3 (Frankfurt) Operational
90 days agoNo incidentsToday
us-central1 (Iowa) Operational
90 days agoNo incidentsToday
asia-northeast1 (Tokyo) Operational
90 days agoNo incidentsToday

Azure

East US (Virginia) Operational
90 days agoNo incidentsToday
Germany West Central (Frankfurt) Operational
90 days agoNo incidentsToday
Central US (Iowa) Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

No incident in the last 90 days.

Follow Zilliz

Your coding agent knows when Zilliz is down, and tells you when a failure is theirs, not yours. You can also get Zilliz incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "zilliz" and tell me if Zilliz has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=zilliz
Slack
/feed subscribe https://outages.cc/feed.xml?providers=zilliz

Go from tracking outages to fixing production issues with Polylane.

Try Polylane