Skip to main content
Vendor reliability

Vendor record

Azure Cosmos DB

Vendor reports Operational

Checked

Front door check counts and Azure Cosmos DB’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We have no front door checks against Azure Cosmos DB in the last 30 days. That does not show whether it was reachable.

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Azure Cosmos DB product, region or your app worked.

How we count front door checks

Azure Cosmos DB says

Incident posts from Azure Cosmos DB’s status page, with its titles, impact levels and times. They say what Azure Cosmos DB chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

Azure publishes its status as an RSS feed with no per-service breakdown, so incidents shown here are Azure-wide rather than specific to this product. We do not guess which product an Azure incident touched.

12

incidents Azure Cosmos DB posted, last 180 days

Median recorded duration: 1h 27m. From 12 incidents with vendor-supplied starts and recorded closure times.

All vendors’ incidents

Most recent records · all dates

  • Active -Azure Data Factory – Pipeline/Activity Failures and Timeouts – UK South

    Minor

    Started, per Azure Cosmos DB

    Closed in our record(1h 27m)

    Azure Cosmos DB’s post

  • Active -Azure Data Factory – Pipeline/Activity Failures, Delays & Timeouts – UK South

    Minor

    Started, per Azure Cosmos DB

    Closed in our record(11m)

    Azure Cosmos DB’s post

  • Active - Multiple services experiencing connectivity issues in multiple regions

    Minor

    Started, per Azure Cosmos DB

    Closed in our record(6h 5m)

    Azure Cosmos DB’s post

  • Active - ExpressRoute Gateway - Multiple services experiencing connectivity issues in multiple regions

    Minor

    Started, per Azure Cosmos DB

    Closed in our record(2h 50m)

    Azure Cosmos DB’s post

  • Active - Azure ExpressRoute Gateway service impacting event in multiple Azure Regions

    Minor

    Started, per Azure Cosmos DB

    Closed in our record(2h 30m)

    Azure Cosmos DB’s post
7 older records

  • Observing improvements - Intermittent request failures and increased latency across Azure OpenAI, Azure AI Foundry, and Cognitive Services

    Minor

    Started, per Azure Cosmos DB

    Closed in our record(9h)

    Azure Cosmos DB’s post

  • Intermittent request failures and increased latency across Azure OpenAI, Azure AI Foundry, and Cognitive Services

    Minor

    Started, per Azure Cosmos DB

    Closed in our record(7h 10m)

    Azure Cosmos DB’s post

  • Azure OpenAI and Foundry agent Service intermittent request failures and increased latency

    Minor

    Started, per Azure Cosmos DB

    Closed in our record(5h)

    Azure Cosmos DB’s post

  • Active - Network Infrastructure impacting event in East US

    Minor

    Started, per Azure Cosmos DB

    Closed in our record(16m)

  • Active -Multiple Service impacted affecting West US Regions

    Major

    Started, per Azure Cosmos DB

    Closed in our record(15m)

  • Investigating- Issues in Southeast Asia

    Major

    Started, per Azure Cosmos DB

    Closed in our record(17m)

  • Active -Azure Portal access issues affecting Australia Regions

    Major

    Started, per Azure Cosmos DB

    Closed in our record(22m)

Your code, your dependencies

See which of your code paths call Azure Cosmos DB

Connect GitHub or GitLab to find where your public or private repository uses Azure Cosmos DB. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add Azure Cosmos DB status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · Azure Cosmos DBStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/azure-cosmos?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Azure Cosmos DB status badge"></iframe>

Frequently Asked Questions

Is Azure Cosmos DB currently down?

Azure Cosmos DB's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did Azure Cosmos DB last have an outage?

The most recent closed incident record began 8 days ago and spans 1h 27m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for Azure Cosmos DB?

No. CheckUpstream does not run front door checks against Azure Cosmos DB. The incident history on this page is what Azure Cosmos DB reported, not a measure of how often it was available.

How do I monitor Azure Cosmos DB in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track Azure Cosmos DB?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.

Related vendors