- Level
- confirmed
- Worst impact
- Operational
- Components
- MongoDB Cloud
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 0m it lasted.
Anything that failed between 2026-06-25 10:16 UTC and 2026-06-25 10:16 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 1
- resolved
From 2026-06-25 06:55 UTC to 2026-06-25 07:10 UTC, some users may have experienced intermittent Atlas UI loading failures. We identified elevated traffic to a number of endpoints that increased latency in the Atlas UI service. This caused internal health checks to fail and temporarily reduced healthy Atlas UI capacity. We restored healthy Atlas UI capacity and applied additional rate limiting to the affected traffic paths. We are continuing follow-up work to further reduce the risk of recurrence.
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-ee5af96ac5
Is MongoDB Atlas still down?
No, this incident was resolved 2026-06-25 10:16 UTC. For MongoDB Atlas's live state, see https://down.guide/mongodb-atlas.
How long did it last?
0m, from 2026-06-25 10:16 UTC to 2026-06-25 10:16 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.