- Level
- confirmed
- Worst impact
- Degraded
- Components
- MongoDB Cloud
- Down Index
- 17of 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 23m it lasted.
Anything that failed between 2026-07-02 10:45 UTC and 2026-07-02 11:09 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 the issue where AWS cluster backup and restores are failing. This includes exports and manual downloads as well as restoring to another cluster. We are also investigation potential impact to other operations on AWS clusters such as modifying instance size.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved. AWS clusters should no longer encounter errors during backup and restore.
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-8a5e7ad902
Is MongoDB Atlas still down?
No, this incident was resolved 2026-07-02 11:09 UTC. For MongoDB Atlas's live state, see https://down.guide/mongodb-atlas.
How long did it last?
23m, from 2026-07-02 10:45 UTC to 2026-07-02 11:09 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.