07:30 AM
The cleanup operation was initiated.
07:50 AM
Initial customer impact began, and increased over the next 90 minutes.
08:13 AM
Our telemetry detected resource availability loss across multiple AFD edge sites. We began investigating as impact continued to grow.
09:04 AM
We identified that the crashes were due to the previously identified data plane bug.
09:08 AM
Automated restarts began for our AFD infrastructure resources, and manual intervention began for resources that did not recover automatically.
09:15 AM
Customer impact had grown to be at its peak.
10:01 AM
Communications were published to the Azure Status page.
10:45 AM
Targeted customer communications were sent to Azure Service Health.
11:59 AM
Management portals, like the Azure Portal, performed failover operations (including using scripts to update the load balancing configuration, to split traffic between multiple routes) helping restore its service availability.
12:50 PM
Availability for AFD fully recovered, however a subset of customers may still have been experiencing elevated latency.
04:00 PM
After continuous monitoring of latency improvement, we declared the incident as mitigated after confirming recovery.