Alkira incident

Networking issues impacting Azure Services in East US2

Minor Resolved View vendor source →

Alkira experienced a minor incident on January 9, 2025 affecting USEAST-AZURE-2 (Virginia), lasting 1d 7h. The incident has been resolved; the full update timeline is below.

Started
Jan 09, 2025, 03:33 PM UTC
Resolved
Jan 10, 2025, 10:45 PM UTC
Duration
1d 7h
Detected by Pingoru
Jan 09, 2025, 03:33 PM UTC

Affected components

USEAST-AZURE-2 (Virginia)

Update timeline

  1. investigating Jan 09, 2025, 03:33 PM UTC

    Azure has reported having networking infrastructure issues in East US2. While the issue does not impact existing network status, we are posting this here so that our customers are aware of this. New provision might have failures related to East US2. https://azure.status.microsoft/en-gb/status Summary of Impact from Azure: As early as 22:00 UTC on 08 Jan 2025, we noticed a partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. The configuration change caused inconsistent service state. This could have resulted in intermittent Virtual machine connectivity issues or failures in allocating resources or communicating with resources in the region.

  2. monitoring Jan 09, 2025, 07:01 PM UTC

    Services are responding well, and the impact is minimal. We continue to monitor the status. https://azure.status.microsoft/en-gb/status

  3. resolved Jan 10, 2025, 10:45 PM UTC

    Most of the services are fully functional in Azure East US2. Please reach out if you are still having issues. This incident is closed.