- Level
- confirmed
- Worst impact
- Degraded
- Components
- MongoDB Atlas Stream Processing
- Regions
- us, us-east-1
- Down Index
- 16of 100
What to do
Check whether you use MongoDB Atlas MongoDB Atlas Stream Processing in us, us-east-1. 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-03-11 20:10 UTC and 2026-03-11 20:10 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
At approximately 10:30 AM CT, we identified an issue affecting stream processing within the AWS US-EAST-1 region. As of now, normal operations have resumed. We have initiated a full investigation to determine the root cause and prevent future 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-62fed48be2
Is MongoDB Atlas still down?
No, this incident was resolved 2026-03-11 20:10 UTC. For MongoDB Atlas's live state, see https://down.guide/mongodb-atlas.
How long did it last?
0m, from 2026-03-11 20:10 UTC to 2026-03-11 20:10 UTC, by the times MongoDB Atlas posted.
What was affected?
MongoDB Atlas named MongoDB Atlas Stream Processing in us, us-east-1.
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.