Azure status history
Product:
Region:
Date:
July 2025
Mitigated - WAN issue - Multiple Services - West US (Tracking ID PTW8-PSZ)
Between 18:00 UTC and 23:30 UTC on 10 July 2025, customers may have experienced connectivity issues in the West US region, impacting multiple services including Virtual Machines, App Services, Azure OpenAI, Azure Storage, SQL Database, and Azure Notification Hub.
This issue is now mitigated. Further details will be provided shortly.
June 2025
Mitigated: Multiple Services experiencing availability issues - East US (Tracking ID CMP9-9CG)
What happened?
Between 12:00 UTC and 15:00 UTC on 23 June 2025, Azure experienced an issue impacting multiple services in East US. Customers may have experienced connectivity issues, such as availability degradation, timeouts, and/or errors when attempting to connect to resources hosted in this region.
What do we know so far?
We identified a recent change to a WAN router in the region, which resulted in a bug that prevented traffic from traversing the geography. This caused customer traffic to experience pack drops when attempting to route through this device.
How did we respond?
- 12:00 UTC on 23 June 2025 - Customer impact began
- 12:30 UTC on 23 June 2025 - Service monitoring detected a drop in networking traffic success for the unhealthy device
- 12:55 UTC on 23 June 2025 - We identified through recent change logs, an unhealthy deployment that included a regression
- 14:00 UTC on 23 June 2025 - We began to isolate the unhealthy network device and reroute traffic to other devices in the geography
- 15:00 UTC on 23 June 2025 - All services confirmed recovery, and telemetry validate network health restored to normal
What happens next?
- Our team will be completing an internal retrospective to understand the incident in more detail. We will publish a Preliminary Post Incident Review (PIR) within approximately 72 hours, to share more details on what happened and how we responded. After our internal retrospective is completed, generally within 14 days, we will publish a Final Post Incident Review with any additional details and learnings.
- To get notified when that happens, and/or to stay informed about future Azure service issues, make sure that you configure and maintain Azure Service Health alerts – these can trigger emails, SMS, push notifications, webhooks, and more: https://aka.ms/ash-alerts
- For more information on Post Incident Reviews, refer to https://aka.ms/AzurePIRs
- The impact times above represent the full incident duration, so are not specific to any individual customer. Actual impact to service availability may vary between customers and resources – for guidance on implementing monitoring to understand granular impact: https://aka.ms/AzPIR/Monitoring
- Finally, for broader guidance on preparing for cloud incidents, refer to https://aka.ms/incidentreadiness
sending update (Tracking ID CNNY-9CZ)
Your virtual machine(s) are scheduled for upcoming maintenance. You can choose to proactively initiate the maintenance on your virtual machines to control the exact time of the impact. This option will be available until DD-MMM-YY. Otherwise, the Azure platform will initiate a scheduled reboot between DD-MMM-YY and DD-MMM-YY.
May 2025
testFFSec (Tracking ID Z_WH-3TG)
testMC
V1 Test (Tracking ID SNCL-HZG)
V1 Test
nduckworth - test event for status & banner (Tracking ID DMGK-3SZ)
nduckworth - test event for status & banner