Incidents

Quoted from each provider's status page.

OngoingAll clear
Where, last 284 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 · 14 places · 4 not pinned
Virginia (us-east-1): 6 incidents · AWSFrankfurt (eu-central-1): 2 incidents · AWSOregon (us-west-2): 2 incidents · AWSSão Paulo (sa-east-1): 2 incidents · AWSDublin (eu-west-1): 1 incident · AWSLondon (eu-west-2): 1 incident · AWSMadrid (eu-south-2): 1 incident · AWSMumbai (ap-south-1): 1 incident · AWSParis (eu-west-3): 1 incident · AWSStockholm (eu-north-1): 1 incident · AWSTokyo (ap-northeast-1): 1 incident · AWSZurich (eu-central-2): 1 incident · AWSBahrain (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 · 86 clean
AugSepOctMonWedFri
CleanSev 3–4Sev 2Sev 1

Sat, Aug 151 incident

03:42SEV 2AWS · [RESOLVED] Increased Packet losseu-central-1 · source3d 0h

Wed, Jul 151 incident

23:11SEV 2AWS · [RESOLVED] Elevated connectivity issues with a single Avalability zoneeu-central-1 · source2h 13m