CheckUpstream measured MongoDB Atlas at 100.000% availability across 2821 independent checks (global · atlas-api). 31 incidents were recorded in the past 12 months; the most recent resolved 13 days ago after 1 hour. Status signals are polled from MongoDB Atlas's official Atlassian Statuspage status page, alongside independent probes and community reports. MongoDB Atlas publishes 1 product-level SLA uptime commitment (up to 99.995%), and service credits must be claimed within 0 days of a breach.
90 days measured availability how this is computed
100.000%
global · atlas-api · n=2821 · p95 588ms (30d)
Share of our own checks against MongoDB Atlas endpoints that returned MongoDB Atlas's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 11 incidents · 89 of 90 days with none posted · 20m of declared impact
Fewer incidents in the last 30 days than 21% of 232 tracked services.
Share of each window with no impact declared by MongoDB Atlas
7d
100.000%
30d
99.952%
90d
99.984%
180d
94.720%
1y
87.973%
Downtime like this can be refundable
If you're a paying MongoDB Atlas customer, outages in these windows may count against MongoDB Atlas's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your MongoDB Atlas entitlement →Does MongoDB Atlas actually matter to you?
A MongoDB Atlas outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 11 incidents MongoDB Atlas published and resolved in the last 90 days, measured between their own start and resolution times. It describes how long MongoDB Atlas takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 18, 14:10 UTC · resolved in 1h 9m · Resolved
Aug 5, 05:17 UTC · resolved in 7h 2m · Resolved
Aug 3, 18:47 UTC · resolved in 2h 32m · Resolved
1signal across 1 source
Synthetic probes 1
All of these are CheckUpstream's own probes. Nobody else has reported MongoDB Atlas in this window, so nothing here is corroboration.
Live MongoDB Atlas status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/mongodb-atlas)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
MongoDB Atlas is currently Operational. CheckUpstream tracks MongoDB Atlas in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is MongoDB Atlas down" view? See the MongoDB Atlas Live status page.
Jul 29, 18:55 UTC · resolved in 44m · Resolved
Jul 2, 19:34 UTC · resolved in 0m · Monitoring
Jun 2, 23:00 UTC · resolved in 1h 20m · Resolved
May 28, 22:02 UTC · resolved in 1h 28m · Resolved
May 23, 19:48 UTC · resolved in 6h 22m · Resolved
May 22, 20:32 UTC · resolved in 1h 47m · Resolved
May 8, 19:33 UTC · resolved in 2h 36m · Resolved
May 8, 02:24 UTC · resolved in 1d 12h · Resolved
May 7, 15:17 UTC · resolved in 8h 4m · Resolved
May 6, 21:48 UTC · resolved in 1d 1h · Resolved
Apr 27, 17:16 UTC · resolved in 3h 33m · Resolved
MongoDB Atlas's last resolved incident started 13 days ago and lasted 1h 9m (degraded performance).
MongoDB Atlas's 30-day measured availability is 100.000%, from CheckUpstream's own probes against MongoDB Atlas endpoints. It is the share of checks that returned the expected response, not a figure taken from MongoDB Atlas's status page.
Sign up to CheckUpstream and add MongoDB Atlas to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll MongoDB Atlas's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.