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 places · 1 not pinned
Tokyo (ap-northeast-1): 1 incident · AWSVirginia (us-east-1): 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 · 89 clean
AugSepOctMonWedFri
CleanSev 3–4Sev 2Sev 1

Fri, Aug 211 incident

02:02SEV 4AWS · [RESOLVED] Increased Error Ratesap-northeast-1 · source38m

Fri, Jul 171 incident

08:33SEV 4AWS · [RESOLVED] Inaccurate Estimated Billing Dataaws · source29h 24m

Wed, Feb 251 incident

18:14SEV 4AWS · [RESOLVED] Intermittent missing or delayed EC2 instance and status check metricsus-east-1 · source2h 37m