Who, last 224 days Clean: Microsoft AzureWhere, last 224 days Places 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 · 20 places · 3 not pinned
Virginia (us-east-1): 4 incidents · AWS Frankfurt (eu-central-1, europe-west3): 3 incidents · AWS, Google Cloud Oregon (us-west-2, us-west1): 3 incidents · AWS, Google Cloud Iowa (us-central1): 2 incidents · Google Cloud London (europe-west2, eu-west-2): 2 incidents · Google Cloud, AWS Mumbai (ap-south-1): 2 incidents · AWS, Google Cloud Amsterdam (europe-west4): 1 incident · Google Cloud Chennai: 1 incident · Google Cloud Delhi: 1 incident · Google Cloud Madrid (eu-south-2): 1 incident · AWS Melbourne (australia-southeast2): 1 incident · Google Cloud nam5: 1 incident · Google Cloud Paris (eu-west-3): 1 incident · AWS São Paulo (sa-east-1): 1 incident · AWS Stockholm (eu-north-1): 1 incident · AWS Sydney (australia-southeast1): 1 incident · Google Cloud Tokyo (ap-northeast-1): 1 incident · AWS Toronto (northamerica-northeast2): 1 incident · Google Cloud Bahrain (me-south-1): down now, 1 incident · AWS Dubai (me-central-1): down now, 1 incident · AWS Last 90 days One square per UTC day, coloured by the worst incident that day. Ongoing incidents count today. 0 Sev 1 days · 88 clean
Clean Sev 3–4 Sev 2 Sev 1
Tue, Oct 201 incident 06:00 SEV 2 Google Cloud · Multiple services were experiencing issues in the europe-west2 region.europe-west2 · postmortem · source 6h 10m Wed, Aug 191 incident 15:15 SEV 3 AWS · [RESOLVED] Increased Error Rateseu-west-2 · source 3h 32m