Incidents

Quoted from each provider's status page.

OngoingAll clear
Who, last 224 days
CGoogle Cloud16h 10mBAWS10m
Clean: Microsoft Azure
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 · 20 places · 3 not pinned
Virginia (us-east-1): 4 incidents · AWSFrankfurt (eu-central-1, europe-west3): 3 incidents · AWS, Google CloudOregon (us-west-2, us-west1): 3 incidents · AWS, Google CloudIowa (us-central1): 2 incidents · Google CloudLondon (europe-west2, eu-west-2): 2 incidents · Google Cloud, AWSMumbai (ap-south-1): 2 incidents · AWS, Google CloudAmsterdam (europe-west4): 1 incident · Google CloudChennai: 1 incident · Google CloudDelhi: 1 incident · Google CloudMadrid (eu-south-2): 1 incident · AWSMelbourne (australia-southeast2): 1 incident · Google Cloudnam5: 1 incident · Google CloudParis (eu-west-3): 1 incident · AWSSão Paulo (sa-east-1): 1 incident · AWSStockholm (eu-north-1): 1 incident · AWSSydney (australia-southeast1): 1 incident · Google CloudTokyo (ap-northeast-1): 1 incident · AWSToronto (northamerica-northeast2): 1 incident · Google CloudBahrain (me-south-1): down now, 1 incident · AWSDubai (me-central-1): down now, 1 incident · AWS
Last 90 daysOne square per UTC day, coloured by the worst incident that day. Ongoing incidents count today.
0 Sev 1 days · 88 clean
AugSepOctMonWedFri
CleanSev 3–4Sev 2Sev 1

Tue, Oct 201 incident

06:00SEV 2Google Cloud · Multiple services were experiencing issues in the europe-west2 region.europe-west2 · postmortem · source6h 10m

Wed, Aug 191 incident

15:15SEV 3AWS · [RESOLVED] Increased Error Rateseu-west-2 · source3h 32m