- Level
- confirmed
- Worst impact
- Operational
- Components
- MongoDB Cloud
- Regions
- us
What to do
Check whether you use MongoDB Atlas MongoDB Cloud in us. 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 1h 23m it lasted.
Anything that failed between 2026-03-30 21:47 UTC and 2026-03-30 23: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 2
- identified
Identified: Some clusters in the Azure East US 2 region will see delays provisioning new clusters or adding additional nodes to their existing clusters due to Azure capacity constraints. What you might see: Delays in provisioning new clusters or adding additional nodes in Azure East US 2 region. User action: As a workaround, users can provision clusters in other Azure regions.
provider
- resolved
We are no longer seeing capacity issues in Azure East US 2. This issue is now resolved.
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-1bda90cb9a
Is MongoDB Atlas still down?
No, this incident was resolved 2026-03-30 23:10 UTC. For MongoDB Atlas's live state, see https://down.guide/mongodb-atlas.
How long did it last?
1h 23m, from 2026-03-30 21:47 UTC to 2026-03-30 23:10 UTC, by the times MongoDB Atlas posted.
What was affected?
MongoDB Atlas named MongoDB Cloud in us.
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.