Is MongoDB Atlas down?
Right now
Yes. MongoDB Atlas has a partial outage.
Impaired Cluster operations in AWS me-central-1 and AWS me-south-1.
Read from status.mongodb.com · every 120s
For agents
fallback
Use a fallback, next attempt in 300s.
GET upbutler.com/status/mongodb-atlas/status.agent.json
MCP: upstream_status {"service":"mongodb-atlas"}
Managed MongoDB clusters, Atlas Search and App Services.
What MongoDB Atlas reports
Partial outage· 1 open incident
Taken as is from MongoDB Atlas's own status page API. Incident titles and component names below are theirs.
Open status.mongodb.comUpButler's independent probe
There is no keyless endpoint of MongoDB Atlas that says anything useful, so UpButler does not probe it. To check your own MongoDB Atlas account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Open at MongoDB Atlas
- Impaired Cluster operations in AWS me-central-1 and AWS me-south-1monitoring · impact major
Since · MongoDB Cloud
We are continuing to monitor for any further issues.
Text written by MongoDB Atlas, shown unchanged.
MongoDB Atlas components
10 operational
- 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
- VoyageAI Embedding and Reranking ModelsOperational
- MongoDB Atlas Agent EngineOperational
MongoDB Atlas incidents, last 90 days
5 finished incidents seen since UpButler started tracking on 2026-10-10, 2 of them rated major or critical by MongoDB Atlas. A typical one lasted 2 h 35 min; the longest 5 h 13 min.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| Issue impacting Atlas Search availability on certain clusters | major | 1 h 48 min | |
| Admin Admin API: Intermittent Increase in 5xx errors | none | 2 h 35 min | |
| MongoDB Charts: Infinite login loop when creating new Charts projects | minor | 5 h | |
| Trigger processing may be delayed globally | major | 5 h 13 min | |
| Delays in Atlas cluster management operations | none | 2 h 10 min |
Tell your outage from MongoDB Atlas's
Declare that your project depends on MongoDB Atlas. When one of your monitors fails while MongoDB Atlas has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- mongodb-atlascurl -s https://upbutler.com/status/mongodb-atlas/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "mongodb-atlas",
"verdict": "fallback",
"status": "partial_outage",
"reason": "Impaired Cluster operations in AWS me-central-1 and AWS me-south-1",
"retryAfterSec": 300,
"incident": {
"title": "Impaired Cluster operations in AWS me-central-1 and AWS me-south-1",
"url": "https://status.mongodb.com/incidents/yhvvsfvwyf1h"
},
"probe": null
}Questions
- Is MongoDB Atlas down right now?
- Yes. As of 2026-10-10 05:13 UTC, MongoDB Atlas has a partial outage, with an open incident: "Impaired Cluster operations in AWS me-central-1 and AWS me-south-1". This page reads the status again every 2 minutes.
- Where does this status come from?
- From MongoDB Atlas's own status page API at https://status.mongodb.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are MongoDB Atlas's words.
- How can my agent or app check MongoDB Atlas status?
- Fetch https://upbutler.com/status/mongodb-atlas/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"mongodb-atlas"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or MongoDB Atlas's?
- Add "mongodb-atlas" to the dependencies of your UpButler workspace. When one of your monitors fails while MongoDB Atlas has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in databases and data
UpButler is not affiliated with MongoDB Atlas. Status and incident text belong to MongoDB Atlas and are read from their public status source; the probe result is UpButler's own measurement.