Home
Uptime monitoring Observability AI monitoring Real User Monitoring Incident response Integrations & API AI assistants (MCP) Explore the platform →
Pricing
Uptime Calculator Cron Expression Builder HTTP Status Codes Is It Down? All free tools
Platform Blog About Contact FAQ Partners
Sign in Start free

Is MongoDB Atlas down?

Not fully, but MongoDB Atlas is having problems.

MongoDB Atlas’s status page reports “Impaired Cluster operations in AWS me-central-1 and AWS me-south-1” (monitoring), cloud.mongodb.com responded from 6 regions, and nobody reported problems in the last hour.

Last checked Since 03:16 UTC (1 h 5 min) Status changed

  • Official statusMinor issuestatus.mongodb.com
  • Reachable6 of 6 regionsAtlas Admin API · cloud.mongodb.com
  • Reports in the last hour0Normal

Incident on MongoDB Atlas’s status pageMonitoring

Impaired Cluster operations in AWS me-central-1 and AWS me-south-1

We are continuing to monitor for any further issues.

Updated Started MongoDB Cloud

Read the update on status.mongodb.com

Railway and Twilio started having problems within 10 minutes of MongoDB Atlas, so the cause may be shared.

MongoDB Atlas’s status page

From status.mongodb.com. Read at

  • MongoDB CloudOperational
  • MongoDB Support PortalOperational
  • MongoDB Atlas App Services and Device SyncOperational
  • MongoDB Atlas Data Federation and Online ArchiveOperational
  • MongoDB Atlas SearchOperational
  • MongoDB ChartsOperational
  • MongoDB Atlas Stream ProcessingOperational
  • MongoDB Atlas for GovernmentOperational
Show all 10 components
  • VoyageAI Embedding and Reranking ModelsOperational
  • MongoDB Atlas Agent EngineOperational

Not working for me

Pick what’s broken. Reports from everyone show up on the chart below within 5 minutes.

Email me when MongoDB Atlas is down or back

One email when it goes down and one when it’s back. No account, and every email has a one-click unsubscribe.

We use your address only for these alerts. Privacy

Last 24 hours

2 h 50 min with problems in the last 24 hours, median response 321 ms, and 0 reports.

Status
Response time
500 ms0
Reports
4
06:0012:0018:0000:00UTC
  • Operational
  • Degraded
  • Partial outage
  • Major outage
  • No data
  • Reachability check (cloud.mongodb.com)
  • Official incident

By region

RegionAtlas Admin API cloud.mongodb.com
N. Virginia us-east-1401 · 17 ms
Oregon us-west-2401 · 226 ms
Frankfurt eu-central-1401 · 294 ms
Singapore ap-southeast-1401 · 686 ms
Tokyo ap-northeast-1401 · 461 ms
São Paulo sa-east-1401 · 356 ms

Two regions check MongoDB Atlas every minute, and any failure is rechecked from all of them. Each row shows the latest result. How we check

Last 90 days

We have checked MongoDB Atlas ourselves since Oct 28, 2026. Earlier days come from its status page.

Jul 31, 2026Today

90 days with problems in the last 90 days.

Recent incidents

Incidents: 6 in the last 30 days and 14 in the last 90, lasting a median of 2 h 35 min.

  1. GCP Availability Zone europe-west2-b connectivity issuesDegraded12 h 36 min
  2. Issue impacting Atlas Search availability on certain clustersPartial outage1 h 47 min
  3. Admin Admin API: Intermittent Increase in 5xx errorsDegraded2 h 35 min
  4. MongoDB Charts: Infinite login loop when creating new Charts projectsDegraded5 h
  5. Trigger processing may be delayed globallyPartial outage5 h 12 min
  6. Delays in Atlas cluster management operationsDegraded2 h 10 min
  7. Support Portal OutagePartial outage6 h 24 min
  8. Atlas is experiencing issues with issuing certificates from Lets EncryptDegraded2 h 23 min
  9. Impaired Cluster operations in AWS me-central-1 and AWS me-south-1Partial outageOngoing
  10. MongoDB Atlas Log Integration service degradedDegradedunder 1 min

Full MongoDB Atlas outage history

If MongoDB Atlas isn’t working for you

MongoDB Atlas is MongoDB's fully managed cloud database service, running on AWS, Google Cloud and Azure.

Common MongoDB Atlas errors

ErrorWhat it meansUsuallyWhat to do
connection refused because too many open connectionsThe cluster hit its concurrent connection limit for its tier.Your sideClose unused connections, restart the app, or scale to a higher tier. Source
DNSHostNotFound: Failed to look up serviceYour DNS server could not resolve the SRV record used by mongodb+srv:// connection strings.Your sideSwitch to a public DNS server or use a non-SRV connection string. Source
Error: querySrv ECONNREFUSED _mongodb._tcp.<SRV Record>The SRV lookup for your cluster was refused, usually by your network's DNS.Your sideFollow Atlas's troubleshooting steps for SRV lookups or use a standard connection string. Source

Is it just you?

  1. Check that your current IP address is on the project's IP access list; Atlas rejects everyone else.
  2. Confirm the database user, password and authSource in your connection string.
  3. Try a different network or DNS server if SRV lookups fail.
  4. Check status.mongodb.com for cloud and region incidents.

Alternatives to MongoDB Atlas

Questions

The most common causes are an IP address missing from the access list, wrong credentials, DNS that cannot resolve SRV records, or hitting the connection limit. Atlas's troubleshooting page covers each.

MongoDB posts Atlas incidents on its status page. If other clusters or the Atlas UI work, the problem is likely your cluster or network.

Sources: mongodb.com, status.mongodb.com

Do you depend on MongoDB Atlas?

Get alerted when MongoDB Atlas breaks your app.

If your product or your team depends on MongoDB Atlas, its outage is your outage, and your users will blame you, not MongoDB Atlas. Point a Site Qwality monitor at the MongoDB Atlas endpoint you actually rely on, put your own site next to it, and we alert you on Slack, email, SMS or any webhook the moment either one stops answering.

Monitor MongoDB Atlas free Free plan checks every 5 minutes · no credit card

Is something else down?

See every service How we check