Incidents

Quoted from each provider's status page.

OngoingAll clear
Where, last 224 daysPlaces 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 · 5 places · 37 not pinned
Amsterdam (West Europe): 3 incidents · MongoDB AtlasVirginia (us-east-1, East US 2): 2 incidents · MongoDB AtlasLondon (europe-west2): 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 · 90 clean
AugSepOctMonWedFri
CleanSev 3–4Sev 2Sev 1

Fri, May 81 incident

02:24SEV 2MongoDB Atlas · AWS Availability Zone use1-az4 in US-EAST-1 Region is ImpairedMongoDB Cloud · source36h 00m

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