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.
12 places · 1 not pinned
Iowa (us-central1): 2 incidents · Google CloudAmsterdam (europe-west4): 1 incident · Google CloudChennai: 1 incident · Google CloudDelhi: 1 incident · Google CloudFrankfurt (europe-west3): 1 incident · Google CloudLondon (europe-west2): 1 incident · Google CloudMelbourne (australia-southeast2): 1 incident · Google CloudMumbai: 1 incident · Google Cloudnam5: 1 incident · Google CloudOregon (us-west1): 1 incident · Google CloudSydney (australia-southeast1): 1 incident · Google CloudToronto (northamerica-northeast2): 1 incident · Google Cloud
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, Oct 81 incident

11:00SEV 2Google Cloud · Google Cloud Storage (GCS) customers experienced elevated latencies and error rates when performing upload or write operations.us-central1 · postmortem · source29h 46m

Tue, Sep 11 incident

14:42SEV 2Google Cloud · Multiple products in us-central1-b are experiencing network service degradation.nam5, us-central1 · postmortem · source4h 10m