Virtual Machines / Azure Databricks / Azure Database for PostgreSQL- Flexible server / Azure Database for MySQL- Flexible server - East US 2 - Applying Mitigation (Extended)
Resolved
Minor
January 31, 2023 - Started almost 2 years ago
- Lasted about 19 hours
Need to monitor Azure outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including Azure, and never miss an outage again.
Start Free Trial →
Outage Details
As of 07:01 UTC on 31 Jan 2023, customers using Virtual Machines, Databricks, and Azure Database for MySQL- Flexible server in East US 2 may receive error notifications when performing service management operations - such as create, delete, update, scaling, start, stop - for resources hosted in this region. PostgreSQL and MySQL would have also been affected. Workaround: Customers may see Error Code on VMSS operation tracking API is InternalExcecutionError, due to this impact. Customers should still be able to scale out and get the VMs allocated. The failures are mainly in the VM delete and update workflows. Current Status: Automatic monitoring alerted us of two partitions of a backend service hosted in East US 2 region becoming unhealthy due to a data process issue. Due to dependencies between services, this manifests in failures when performing service management operations for a subset of Virtual Machines customers with resources in a single Availability Zone. We are nearing completion of the restoration of the partitions; however, some customers may start seeing improvements at this time. Customer's may attempt to resubmit jobs and enabling automatic retries for these to succeed. If there's an interactive cluster, those resources may need to be restarted. At this time customers should start seeing higher success rates at this time. More information will be made available in 1 hour, or sooner as events warrant.