Cloud UI and login unavailable
Qdrant Cloud reports that the Cloud UI and login do not work. The incident is resolved. It lasted about 1 minute. Existing clusters and database operations were not affected.
State
Resolved
Started
1 h ago
2026-11-02 13:27 UTC
Lasted
1 min
until 2026-11-02 13:27 UTC
Worst impact
Major outage
Timeline
2 updatesResolved
1 min 100%
Updates
Times in UTCAs posted by Qdrant Cloud
We are investigating an issue affecting the Qdrant Cloud UI and login. Users may be unable to sign in or use the Cloud UI. Existing clusters and database operations are not affected and continue to work normally. Our engineering team is actively working on this. We will provide the next update as soon as we have more information.
We are investigating an issue affecting the Qdrant Cloud UI and login. Users may be unable to sign in or use the Cloud UI. Existing clusters and database operations are not affected and continue to work normally. Our engineering team is actively working on this. We will provide the next update as soon as we have more information.
Affected components
1Qdrant Cloud in the last 90 days
Full historyIncidents in 90 days
3
Days with an incident
3
Median duration
Not enough data
This incident
Not comparable
Other Qdrant Cloud incidents
All incidentsQdrant Cloud·Cluster metrics unavailable in AWS us-east-1
Monitoring metrics, including the /sys_metrics endpoint, are currently unavailable for clusters in AWS us-east-1. Clusters keep running, and reads and writes are not affected. We have found the cause in our internal metrics collection and are working on a fix. Metrics will be available again once it is resolved.
Qdrant Cloud·Cluster Availability Issues in Germany West Central
We're investigating an issue affecting Qdrant Cloud clusters in the Azure Germany West Central region. Some clusters are currently unavailable, and others are running with fewer replicas than usual. Our engineers are investigating the issue. You don't need to take any action. Please avoid deleting or recreating your cluster while we work on this. We'll post the next update asap.
Follow Qdrant Cloud
Your coding agent knows when Qdrant Cloud is down, and tells you when a failure is theirs, not yours. You can also get Qdrant Cloud incidents in a feed reader or in Slack.
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 "qdrant" and tell me if Qdrant Cloud 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.
https://outages.cc/feed.xml?providers=qdrant/feed subscribe https://outages.cc/feed.xml?providers=qdrantFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane