Skip to main content
MongoDB Atlas logo

Is MongoDB Atlas Down?

No — MongoDB Atlas is up

Reachable from all 8 checked regions

Average response time: 510ms

Last checked · checks run every 6 hours

Official status page: https://status.mongodb.com

MongoDB Atlas uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
548ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 21 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

21-day clean streak
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 24 checks
Jul 29: 100.00% uptime, 32 checks
Jul 30: 100.00% uptime, 32 checks
Jul 31: 100.00% uptime, 32 checks
Aug 1: 100.00% uptime, 32 checks
Aug 2: 100.00% uptime, 38 checks
Aug 3: 100.00% uptime, 32 checks
Aug 4: 100.00% uptime, 40 checks
Aug 5: 100.00% uptime, 40 checks
Aug 6: 100.00% uptime, 32 checks
Aug 7: 100.00% uptime, 32 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 29 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 16 checks
Jul 19 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
34ms
DNS 2ms TCP 0ms TLS 3ms TTFB 24ms
arn
125ms
DNS 1ms TCP 1ms TLS 7ms TTFB 81ms
bom
2052ms
DNS 1ms TCP 2ms TLS 10ms TTFB 1125ms
cdg
932ms
DNS 0ms TCP 1ms TLS 4ms TTFB 518ms
ord
114ms
DNS 0ms TCP 38ms TLS 22ms TTFB 83ms
sin
33ms
DNS 0ms TCP 1ms TLS 4ms TTFB 19ms
sjc
822ms
DNS 0ms TCP 1ms TLS 3ms TTFB 527ms
syd
31ms
DNS 0ms TCP 1ms TLS 3ms TTFB 17ms
yyz
52ms
DNS 0ms TCP 0ms TLS 2ms TTFB 34ms

What MongoDB Atlas does

MongoDB Atlas is the managed MongoDB service, running clusters on AWS, Google Cloud and Azure. Applications treat it as their primary datastore, so an Atlas incident is rarely a degraded feature: it is an application that cannot read or write anything, returning errors on every request that touches the database.

What an outage looks like

Applications throw connection timeouts or server selection errors as drivers fail to reach a replica set member. Queries that do complete run slowly while a failover is in progress. Atlas Search queries can fail while ordinary reads and writes succeed, because Search is a separate component. The Atlas web console may load normally while clusters stay unreachable.

What to do about it

Check status.mongodb.com, which reports Atlas Search, Data Federation, Charts, Stream Processing and App Services separately from MongoDB Cloud itself, so identify which component your failure actually touches. Drivers retry many operations on their own, so avoid restarting application instances in a loop. Cluster incidents are often confined to one cloud region rather than the whole service.

Is it down for everyone, or just you?

If this page says MongoDB Atlas is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

AWS
AWS
DigitalOcean
DigitalOcean
Datadog
Datadog
Vercel
Vercel

MongoDB Atlas outage FAQ

Is Atlas down or is my connection string wrong?
A server selection timeout looks identical either way. Check status.mongodb.com first, then confirm whether the failure is new: a connection string that never worked points at configuration, IP access lists or credentials, while one that worked ten minutes ago points at the service. Test from a second network to rule out an access list change on your side.
Will I lose writes during a MongoDB Atlas outage?
Writes acknowledged by the cluster are durable and survive a failover, since Atlas replicates across nodes. Writes in flight when connectivity broke may not have landed, and your driver will surface those as errors rather than silently discarding them. Retryable writes, enabled by default in current drivers, replay many of these automatically once a new primary is elected.
Why is Atlas Search failing when my queries work?
Atlas Search runs as its own service on separate infrastructure and is reported as its own status component. A Search incident breaks text search and aggregation stages that use it, while ordinary find and update operations against the same collections continue normally. If only your search feature is broken, check that component before investigating the cluster.
Does an Atlas outage affect every cloud region?
Rarely. Atlas clusters run in specific regions on AWS, Google Cloud or Azure, and most incidents trace back to a problem in one provider's region rather than to Atlas globally. The status page and incident history name the affected regions. A cluster deployed across regions may lose some nodes and keep serving through the rest.
Should I restart my application during an Atlas incident?
Usually not. MongoDB drivers hold a connection pool and reconnect on their own as nodes become reachable, so restarting mostly discards that state and adds a reconnection storm on top of a recovering cluster. Restarting is worth it only when the application has clearly wedged and is no longer retrying after the cluster is healthy.

How we measure this

  • We request MongoDB Atlas's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where MongoDB Atlas publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when MongoDB Atlas goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required