Incidents

Quoted from each provider's status page.

AllHostingAI APIsCloudDatabasesDev toolsDev APIs
Any sevSEV 1SEV 2SEV 3SEV 4
Oregon ×US West leaderboard
OngoingAll clear
Who, Aug 18 – Sep 1, 2026
CGoogle Cloud13h 40m
Clean: AWS, Microsoft Azure
Where, Aug 18 – Sep 1, 2026Places 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 · 7 places
Iowa (us-central1): 1 incident · Google CloudLondon (eu-west-2): 1 incident · AWSnam5: 1 incident · Google CloudOregon (us-west1): 1 incident · Google CloudTokyo (ap-northeast-1): 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 · 87 clean
AugSepOctMonWedFri
CleanSev 3–4Sev 2Sev 1

Thu, Aug 201 incident

15:40SEV 2Google Cloud · We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region.AlloyDB for PostgreSQL, Apigee Edge Public Cloud, Apigee X +24 · postmortem · source3h 40m
NewerOlder