Update - We have implemented changes to the provisioning system that are improving successful cluster creation. We have additional measures that we are working on and hope to have deployed within the next couple of weeks.
Mar 03, 2026 - 15:53 UTC
Mar 03, 2026 - 15:53 UTC
Monitoring - Customers may experience provisioning errors when creating clusters in some Azure regions due to limited Azure compute capacity. Affected regions include, but are not limited to, East US, East US 2, and West US. Azure has not provided an ETA for resolution.
Workaround: Attempt provisioning in an alternate Azure region. If a public access cluster is an option, consider deploying to a nearby AWS or GCP region.
Jan 24, 2026 - 17:18 UTC
Workaround: Attempt provisioning in an alternate Azure region. If a public access cluster is an option, consider deploying to a nearby AWS or GCP region.
Jan 24, 2026 - 17:18 UTC
Monitoring - Per AWS: At around 4:30 AM PST 1 Mar 2026, one of the Availability Zones (mec1-az2) was impacted by objects that struck the data center, creating sparks and fire. At 10:46 PM PST it was confirmed a second AZ (mec1-az3) was impacted by "localized power issues" causing EC2 API and instance launch error in mec1-az1. At 12:52 AM PST 2 Mar 2026, AWS posted that it is not currently possible to launch new instances. The 6:22 AM PST update stated recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region is expected to take at least a day.
We will continue to monitor the situation. We encourage customers to check the AWS Service Health page for the most recent updates.
Mar 02, 2026 - 14:43 UTC
We will continue to monitor the situation. We encourage customers to check the AWS Service Health page for the most recent updates.
Mar 02, 2026 - 14:43 UTC
API
Operational
Console
Operational
Provisioning AWS
Degraded Performance
Provisioning GCP
Operational
Provisioning Azure
Degraded Performance
AWS ec2-ap-northeast-1
Operational
AWS ec2-ap-northeast-2
Operational
AWS ec2-ap-south-1
Operational
AWS ec2-ap-southeast-1
Operational
AWS ec2-ap-southeast-2
Operational
AWS ec2-ca-central-1
Operational
AWS ec2-eu-central-1
Operational
AWS ec2-eu-west-1
Operational
AWS ec2-eu-west-2
Operational
AWS ec2-eu-west-3
Operational
AWS ec2-sa-east-1
Operational
AWS ec2-us-east-1
Operational
AWS ec2-us-west-1
Operational
AWS ec2-us-west-2
Operational
AWS route53
Operational
Google Cloud Platform Google Compute Engine
Operational
Google Cloud Platform Google Cloud Networking
Operational
AWS ec2-eu-north-1
Operational
AWS ec2-us-east-2
Operational
AWS vpc-ap-northeast-1
Operational
AWS vpc-ap-northeast-2
Operational
AWS vpc-ap-south-1
Operational
AWS vpc-ap-southeast-1
Operational
AWS vpc-ap-southeast-2
Operational
AWS vpc-ca-central-1
Operational
AWS vpc-eu-central-1
Operational
AWS vpc-eu-north-1
Operational
AWS vpc-eu-west-1
Operational
AWS vpc-eu-west-2
Operational
AWS vpc-eu-west-3
Operational
AWS vpc-us-east-1
Operational
AWS vpc-us-east-2
Operational
AWS vpc-us-west-1
Operational
AWS vpc-us-west-2
Operational
AWS ec2-me-central-1
Degraded Performance
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.