Solace incident
Service creation issue in AKS EastUS2 (Virginia) Public Region
Solace experienced a major incident on April 24, 2026 affecting Azure - East US 2 (Virginia), lasting 3d 10h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 24, 2026, 08:45 AM UTC
We are currently investigating Service creation failures and node scaling issues in the AKS EastUS2 (Virginia) Public Region, caused by an issue with the Kubernetes API endpoint, in collaboration with Azure support to identify the root cause and resolution.
- identified Apr 24, 2026, 07:49 PM UTC
Azure engineering has determined that the root cause is a networking issue where traffic is not reaching the Kubernetes control plane, and they are actively working on a resolution.
- identified Apr 26, 2026, 04:45 AM UTC
All existing services in the AKS EastUS2 (Virginia) Public Region are currently functioning normally. Service creation in this region has been temporarily disabled while we continue to work with Azure engineering on a resolution. We expect to provide a further update by Monday (EST).
- resolved Apr 27, 2026, 07:07 PM UTC
Service creation in the Azure East US region was impacted due to a platform-level issue introduced by an Azure control plane deployment, affecting provisioning and scaling operations across all availability zones. Azure has fully rolled back the change and confirmed complete service restoration. Service creation functionality is now operating normally.