Who, last 194 days Clean: Google Cloud, Microsoft AzureWhere, last 194 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 · 90 clean
Sat, Jun 61 incident 04:24 SEV 2 AWS · [RESOLVED] Internet Connectivity Issuessa-east-1 · source 0m