Active - Multiple services experiencing connectivity issues in multiple regions

Impact

Starting at 20:30 UTC on 30 September 2026, customers using gateway services may be experiencing degraded or interrupted network connectivity. Customers may see gateways failing to load in the Azure Portal, and may also be experiencing failures or delays with network management operations across the following impacted services: ExpressRoute Gateways Azure Firewall Application Gateways / Web Application Firewall VPN Gateways Azure VMWare Solution (AVS) Current status: The vast majority of previously-impacted regions are showing signs of recovery, we are working to apply configuration changes that were successful in other regions to the remaining five regions: France Central, North Europe, Southeast Asia, UK South, and UK West. Our investigation has identified a correlation between the timing of this incident and infrastructure operating system servicing activity, which has since been paused. The underlying failure mechanism has not yet been confirmed, and we continue to investigate why network service instances became unhealthy and why recovery behavior differed across services. We continue to validate recovery - region by region, and service by service. We will provide additional information within the next 60 minutes, or sooner if events warrant.

Affected service

Affected regions

Timeline

Updates newest first (times in UTC).

1. InvestigatingSep 30, 2026, 8:30 PM UTC

   Starting at 20:30 UTC on 30 September 2026, customers using gateway services may be experiencing degraded or interrupted network connectivity. Customers may see gateways failing to load in the Azure Portal, and may also be experiencing failures or delays with network management operations across the following impacted services: ExpressRoute Gateways Azure Firewall Application Gateways / Web Application Firewall VPN Gateways Azure VMWare Solution (AVS) Current status: The vast majority of previously-impacted regions are showing signs of recovery, we are working to apply configuration changes that were successful in other regions to the remaining five regions: France Central, North Europe, Southeast Asia, UK South, and UK West. Our investigation has identified a correlation between the timing of this incident and infrastructure operating system servicing activity, which has since been paused. The underlying failure mechanism has not yet been confirmed, and we continue to investigate why network service instances became unhealthy and why recovery behavior differed across services. We continue to validate recovery - region by region, and service by service. We will provide additional information within the next 60 minutes, or sooner if events warrant.

Related reading