Incidents

Quoted from each provider's status page.

Ongoing1 open incident
MongoDB AtlasDatabases · MongoDB CloudImpaired Cluster operations in AWS me-central-1 and AWS me-south-1SEV 3since Sep 3, 2026
Where, Mar 18 – Apr 1, 2026Places named on the status page: cloud regions, cities, countries, data centres. An incident naming only a broad area (Europe, APAC) is counted under the map, not pinned.
2 down now · 3 places · 4 not pinned
Virginia (East US 2): 1 incident · MongoDB AtlasBahrain (me-south-1): down now, 1 incident · MongoDB AtlasDubai (me-central-1): down now, 1 incident · MongoDB Atlas
Last 90 daysOne square per UTC day, coloured by the worst incident that day. Ongoing incidents count today.
0 Sev 1 days · 69 clean
AugSepOctMonWedFri
CleanSev 3–4Sev 2Sev 1

Mon, Mar 301 incident

21:47SEV 3MongoDB Atlas · Delays in cluster creation and adding new cluster nodes in Azure East US 2 regionMongoDB Cloud · source1h 23m

Wed, Mar 251 incident

21:31SEV 3MongoDB Atlas · Intermittent 503 Errors on Atlas Admin API and Automation ToolingMongoDB Cloud · source39h 50m

Thu, Mar 193 incidents

18:11SEV 2MongoDB Atlas · 3 incidentsMongoDB Atlas Data Federation and Online Archive, MongoDB Cloud, MongoDB Atlas for Government7d 0h
18:11SEV 2MongoDB Atlas · Issue querying Azure blob storage containers in Atlas Data FederationMongoDB Atlas Data Federation and Online Archive · source1h 09m
14:42SEV 3MongoDB Atlas · MongoDB Atlas: Clusters page failing to loadMongoDB Cloud · source45m
00:24SEV 3MongoDB Atlas · MongoDB Atlas for Government: SSO login failures for some usersMongoDB Atlas for Government · source12d 20h