Statuspy
Databases

Is MongoDB Atlas down right now?

No, it’s up.

MongoDB Atlas appears to be up and running normally.

checked responded in 752msHTTP 200

Over the last 7 days, MongoDB Atlas has answered our automated checks with 100.00% availability and a typical response time of ~806 ms. The most recent outage began 2026-08-03 18:47 UTC and lasted 2h 31m (severity: down).

MongoDB Atlas is the managed version of MongoDB, running clusters across AWS, Google Cloud, and Azure. Because it sits on other clouds, its incidents sometimes trace back to an underlying provider, and they tend to affect one region or cluster tier while the Atlas control plane stays available.

Response time (last 24h)
Last 24hpeak 2220 ms
Incident history (last 90 days)
JunJulAug
  • up
  • slow
  • down
  • no reading
DateDurationSeverity
2h 31mDown
41mDegraded
11mDown
4h 6mDown
2h 7mDegraded
19h 18mDegraded
42mDegraded
26mDegraded
1h 32mDegraded
1h 11mDown
1h 12mDegraded
6h 17mDegraded
1h 45mDegraded
2h 33mDegraded
1d 12hDegraded
6h 57mDown
Uptime
100.00%
7 days
100.00%
30 days
100.00%
90 days
What to do if MongoDB Atlas is down for just you
  • Check your connection limit and pool settings first, since exhausting connections looks exactly like the database being down.
  • Retry with a longer timeout, because a serverless or scale-to-zero instance may simply be waking up.
  • Confirm your credentials and IP allowlist have not changed, as an auth or firewall denial reads as a failed query.
  • Query from another network or client to establish whether the cluster or your route to it is the problem.
Frequently asked questions
Is MongoDB Atlas down right now?
MongoDB Atlas appears to be up and running normally. Last checked 2026-08-05 04:42 UTC (3 minutes ago).
When was MongoDB Atlas's last outage?
The most recent outage began 2026-08-03 18:47 UTC and lasted 2h 31m (severity: down).
What should I do if MongoDB Atlas is down for me?
Check your connection limit and pool settings first, since exhausting connections looks exactly like the database being down. Retry with a longer timeout, because a serverless or scale-to-zero instance may simply be waking up. Confirm your credentials and IP allowlist have not changed, as an auth or firewall denial reads as a failed query. Query from another network or client to establish whether the cluster or your route to it is the problem.
MongoDB Atlas’s official status page

Related services