- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on MongoDB Atlas. 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-08-28 18:34 UTC and 2026-08-28 14:30 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
Between approximately 14:29 UTC and 15:42 UTC on August 28, 2026, log delivery via Atlas Log Integration was impacted due to an internal service issue. Some users may have encountered delayed or missing logs during this window. Log delivery has since returned to normal. We are implementing measures to reduce the risk of this happening again.
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-d8b3f807f0
Is MongoDB Atlas still down?
No, this incident was resolved 2026-08-28 14:30 UTC. For MongoDB Atlas's live state, see https://down.guide/mongodb-atlas.
How long did it last?
0m, from 2026-08-28 18:34 UTC to 2026-08-28 14:30 UTC, by the times MongoDB Atlas posted.
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.