Skip to main content
azuredown

Is Azure Cosmos DB down?

OperationalLast checked Aug 1, 2026, 11:20 AM UTC

Last 90 days

100% uptime · 0 incidents
2026-05-04: operational2026-05-05: operational2026-05-06: operational2026-05-07: operational2026-05-08: operational2026-05-09: operational2026-05-10: operational2026-05-11: operational2026-05-12: operational2026-05-13: operational2026-05-14: operational2026-05-15: operational2026-05-16: operational2026-05-17: operational2026-05-18: operational2026-05-19: operational2026-05-20: operational2026-05-21: operational2026-05-22: operational2026-05-23: operational2026-05-24: operational2026-05-25: operational2026-05-26: operational2026-05-27: operational2026-05-28: operational2026-05-29: operational2026-05-30: operational2026-05-31: operational2026-06-01: operational2026-06-02: operational2026-06-03: operational2026-06-04: operational2026-06-05: operational2026-06-06: operational2026-06-07: operational2026-06-08: operational2026-06-09: operational2026-06-10: operational2026-06-11: operational2026-06-12: operational2026-06-13: operational2026-06-14: operational2026-06-15: operational2026-06-16: operational2026-06-17: operational2026-06-18: operational2026-06-19: operational2026-06-20: operational2026-06-21: operational2026-06-22: operational2026-06-23: operational2026-06-24: operational2026-06-25: operational2026-06-26: operational2026-06-27: operational2026-06-28: operational2026-06-29: operational2026-06-30: operational2026-07-01: operational2026-07-02: operational2026-07-03: operational2026-07-04: operational2026-07-05: operational2026-07-06: operational2026-07-07: operational2026-07-08: operational2026-07-09: operational2026-07-10: operational2026-07-11: operational2026-07-12: operational2026-07-13: operational2026-07-14: operational2026-07-15: operational2026-07-16: operational2026-07-17: operational2026-07-18: operational2026-07-19: operational2026-07-20: operational2026-07-21: operational2026-07-22: operational2026-07-23: operational2026-07-24: operational2026-07-25: operational2026-07-26: operational2026-07-27: operational2026-07-28: operational2026-07-29: operational2026-07-30: operational2026-07-31: operational2026-08-01: operational
2026-05-042026-08-01

What Azure Cosmos DB does - and how it fails

Azure Cosmos DB is the globally distributed NoSQL database behind low-latency, always-on workloads - retail carts, IoT telemetry, session state. Its multi-region replication makes full outages rare; incidents usually appear as elevated latency or rate-limiting in one region, or as write-region failover events for accounts without multi-region writes.

  • Elevated request latency or 503s in one region while other replicas stay healthy
  • Request rate-limiting (429s) during regional capacity or partition events
  • Write-region unavailability forcing manual or automatic failover for single-write-region accounts
  • Indexing or query-engine degradation making reads slow rather than failed

Azure Cosmos DB questions

Is Cosmos DB down right now?

Check the live status above. If your account is multi-region, verify whether errors are confined to one region - the SDK’s preferred-region list may just need a healthy replica ahead of the impaired one.

What SLA does Cosmos DB carry?

Cosmos DB’s SLAs are unusually strong: 99.999% availability for multi-region accounts with multi-region writes, and 99.99% for single-region accounts - covering throughput, consistency, and latency as well as availability. Credits are claimed through Azure support.

Get alerted when Azure Cosmos DB breaks

Instant email the moment we detect an incident - affected services and regions included.

Get outage alerts