- Level
- confirmed
- Worst impact
- Partial outage
- Zilliz Cloud says
- 2023-12-07 08:30 to 10:36 UTC (2h 6m)
- Down Index
- 18of 100
What to do
Check whether your product depends on Zilliz Cloud. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2023-12-07 12:49 UTC and 2023-12-07 08:30 UTC may need a replay.Subscribe to Zilliz Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=zilliz works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Root cause
Due to an an incident, from 8:30 to 10:36 UTC some users were unable to connect to their clusters over private links.Read the postmortem
Updates from Zilliz Cloud 1
- 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 systems continued operating normally.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-598d540781
Is Zilliz Cloud still down?
No, this incident was resolved 2023-12-07 08:30 UTC. For Zilliz Cloud's live state, see https://down.guide/providers/zilliz.
How long did it last?
0m, from 2023-12-07 12:49 UTC to 2023-12-07 08:30 UTC, by the times Zilliz Cloud posted.
What caused it?
Zilliz Cloud wrote: "Due to an an incident, from 8:30 to 10:36 UTC some users were unable to connect to their clusters over private links." The postmortem: https://stspg.io/kcq5vl9ws35s
Where does this come from?
Zilliz Cloud's official status page, https://status.zilliz.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.