- Level
- confirmed
- Worst impact
- Degraded
- Components
- MongoDB Cloud
- Down Index
- 25of 100
What to do
Check whether you use MongoDB Atlas MongoDB Cloud. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 19h 19m it lasted.
Anything that failed between 2026-07-09 19:37 UTC and 2026-07-10 14:56 UTC may need a replay.Subscribe to MongoDB Atlas's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=mongodb-atlas works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from MongoDB Atlas 3
- investigating
We are currently investigating issues related to certificate issuing failures with Lets Encrypt. Tenant cluster provisioning is currently impacted.
provider
- monitoring
We are no longer seeing failures with cert issuance from Lets Encrypt. We are still investigating the root cause of the original errors and will continue to monitor.
provider
- resolved
Let's Encrypt service has returned to normal.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-e46c2d142a
Is MongoDB Atlas still down?
No, this incident was resolved 2026-07-10 14:56 UTC. For MongoDB Atlas's live state, see https://down.guide/mongodb-atlas.
How long did it last?
19h 19m, from 2026-07-09 19:37 UTC to 2026-07-10 14:56 UTC, by the times MongoDB Atlas posted.
What was affected?
MongoDB Atlas named MongoDB Cloud.
What caused it?
MongoDB Atlas hasn't published a root cause. If it does, it shows here.
Where does this come from?
MongoDB Atlas's official status page, https://status.mongodb.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.