outages.live
Live
Qdrant CloudIncident · 2026-10-17 20:22 UTC

Cluster metrics unavailable in AWS us-east-1

ResolvedOfficial update

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.

The latest update from Qdrant Cloud.

State

Resolved

Started

16 d ago

2026-10-17 20:22 UTC

Lasted

1 min

until 2026-10-17 20:22 UTC

Worst impact

Degraded

Timeline

1 update
20:2220:2220:2220:2220:23
NoticeUpdate postedTimes in UTC

Resolved

1 min 100%

Updates

Times in UTC

As posted by Qdrant Cloud

Resolved2026-10-17 20:22 UTC

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.

Affected components

2
Cloud UIAWS us-east-1

Qdrant Cloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

3

Days with an incident

3

Median duration

Not enough data

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

1 min
90 days agoToday

Other Qdrant Cloud incidents

All incidents

Qdrant Cloud·Cloud UI and login unavailable

Qdrant Cloud reports that the Cloud UI and login do not work. Users may not sign in or use the Cloud UI. Existing clusters and database operations continue to work normally. Qdrant Cloud states that the incident is resolved.

Resolvedresolved 3 h ago

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.

Resolvedresolved 25 d ago

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.

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.live/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.

RSS
https://outages.live/feed.xml?providers=qdrant
Slack
/feed subscribe https://outages.live/feed.xml?providers=qdrant

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane