Where does this status come from?

From Qdrant Cloud's own status page API at https://status.qdrant.io. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Qdrant Cloud's words.

How can my agent or app check Qdrant Cloud status?

Fetch https://upbutler.com/status/qdrant/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"qdrant"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Qdrant Cloud's?

Add "qdrant" to the dependencies of your UpButler workspace. When one of your monitors fails while Qdrant Cloud has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Qdrant Cloud down?

Right now

No. Qdrant Cloud is operational.

No incidents reported.

Read from status.qdrant.io 72 s ago · every 300s

For agents

proceed

Proceed.

GET upbutler.com/status/qdrant/status.agent.json

MCP: upstream_status {"service":"qdrant"}

Managed Qdrant vector search clusters.

What Qdrant Cloud reports

Operational

Taken as is from Qdrant Cloud's own status page API. Incident titles and component names below are theirs.

Open status.qdrant.io

UpButler's independent probe

There is no keyless endpoint of Qdrant Cloud that says anything useful, so UpButler does not probe it. To check your own Qdrant Cloud account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Qdrant Cloud components

29 operational

Current status by service

Website / DocumentationOperational
Cloud UIOperational
Cloud API (extern)Operational

Cloud Qdrant Database Clusters

AWS us-east-1Operational
GCP europe-west3Operational
Azure southeastasiaOperational
Azure uksouthOperational
Azure germanywestcentralOperational
Azure eastusOperational
Hybrid CloudOperational
AWS us-west-1Operational
Azure westus2Operational
GCP us-east4Operational
AWS us-west-1Operational
AWS us-west-2Operational
AWS eu-central-1Operational
AWS eu-west-1Operational
AWS eu-west-2Operational
AWS ap-northeast-1Operational
AWS ap-southeast-1Operational
AWS ap-southeast-2Operational
Azure japaneastOperational
AWS us-east-2Operational
AWS ca-central-1Operational
AWS sa-east-1Operational
AWS ap-south-1Operational
GCP us-central1Operational
GCP australia-southeast1Operational
GCP europe-west6Operational

Qdrant Cloud incidents, last 90 days

1 finished incident seen since UpButler started tracking on 2026-10-10.

Started (UTC)	Incident	Impact	Lasted
2026-10-08 10:07	Cluster Availability Issues in Germany West Central	minor	under a minute

Tell your outage from Qdrant Cloud's

Declare that your project depends on Qdrant Cloud. When one of your monitors fails while Qdrant Cloud has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - qdrant

Ask before you retry

curl -s https://upbutler.com/status/qdrant/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "qdrant",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Qdrant Cloud down right now?: No. As of 2026-10-10 05:11 UTC, Qdrant Cloud is operational. This page reads the status again every 5 minutes.
Where does this status come from?: From Qdrant Cloud's own status page API at https://status.qdrant.io. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Qdrant Cloud's words.
How can my agent or app check Qdrant Cloud status?: Fetch https://upbutler.com/status/qdrant/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"qdrant"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Qdrant Cloud's?: Add "qdrant" to the dependencies of your UpButler workspace. When one of your monitors fails while Qdrant Cloud has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in databases and data

UpButler is not affiliated with Qdrant Cloud. Status and incident text belong to Qdrant Cloud and are read from their public status source; the probe result is UpButler's own measurement.