Incidents

Quoted from each provider's status page.

OngoingAll clear
Who, last 374 days
BAWS10mAPlanetScale10m
Clean: 37 providers
Where, last 374 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.
4 places · 135 not pinned
Oregon: 2 incidents · RenderVirginia (us-east-1): 2 incidents · PlanetScale, AWSSingapore (Southeast Asia): 1 incident · RailwayTokyo (ap-northeast-1): 1 incident · AWS

Region only: Europe 3 · Asia Pacific 1

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

Tue, Oct 201 incident

19:38SEV 4PlanetScale · Gap in dashboard metrics for AWS us-east-1 · source1h 08m

Wed, Feb 251 incident

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