Palo Alto Networks incident
Service degradation in westus2 due to Azure cloud service issue
Palo Alto Networks experienced a minor incident on May 29, 2026 affecting westus2, lasting 19h 22m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 29, 2026, 08:26 AM UTC
Azure is having service degradation impacting multiple services in the region westus2(https://azure.status.microsoft/en-us/status) We are continuously monitoring the status.
- identified May 29, 2026, 09:46 AM UTC
Latest update from Azure: Mitigation efforts are underway to restore affected network components across dependent services, including Storage and Compute. Customers may begin to see signs of recovery as these actions progress
- identified May 29, 2026, 01:33 PM UTC
Latest update from Azure: Recovered Azure services: Service Bus, Storage, App Service (Web Apps), Azure Site Recovery, Virtual Machine, Virtual Machine scale set, Backup (MAB), Azure Cosmos DB, Azure Log Analytics, Application Insights, Azure Monitor, Azure Resource Manager, Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Kubernetes Service, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Synapse, Azure Database for MySQL - Flexible Server Mitigation efforts are still underway to restore affected network components across dependent services, including Storage and Compute
- resolved May 30, 2026, 03:49 AM UTC
Azure team confirmed that this incident had been resolved.