Incidents

Quoted from each provider's status page.

OngoingAll clear
Where, Feb 18 – Mar 4, 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 places · 1 not pinned
Bahrain (me-south-1): 1 incident · MongoDB AtlasDubai (me-central-1): 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 · 84 clean
AugSepOctMonWedFri
CleanSev 3–4Sev 2Sev 1

Sun, Mar 11 incident

19:30SEV 2MongoDB Atlas · Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)MongoDB Cloud · source185d 21h

Sat, Feb 281 incident

19:53SEV 2MongoDB Atlas · MongoDB App Services: Connectivity issuesMongoDB Atlas App Services and Device Sync · source31h 11m