Final Update: Friday, 21 June 2019 03:48 UTC
We've confirmed that all systems are back to normal with no customer impact as of 6/21, 3:40 AM UTC. Our logs show the incident started on 6/21, 1:32 AM UTC and that during the ~2 hours that it took to resolve the issue, all customers in Fairfax ( USGOV) region experienced Data access issues.
-Anupama
We've confirmed that all systems are back to normal with no customer impact as of 6/21, 3:40 AM UTC. Our logs show the incident started on 6/21, 1:32 AM UTC and that during the ~2 hours that it took to resolve the issue, all customers in Fairfax ( USGOV) region experienced Data access issues.
- Root Cause: The failure was due to invalid configuration file preventing requests to reach their proper backend service.
- Incident Timeline: 2 Hours & 10 minutes - M/D, 6/21,1:32 AM UTC through 6/21,3:40 AM UTC
-Anupama
Initial Update: Friday, 21 June 2019 02:44 UTC
We are aware of issues within Application Insights and Log Analytics and we are actively investigating. All customers in Fairfax ( USGOV region) may experience Data Access issues.
-Anupama
We are aware of issues within Application Insights and Log Analytics and we are actively investigating. All customers in Fairfax ( USGOV region) may experience Data Access issues.
- Work Around: None
- Next Update: Before 06/21 05:00 UTC
-Anupama
Updated Jun 21, 2019
Version 3.0Azure-Monitor-Team
Former Employee
Joined February 13, 2019
Azure Monitor Status Archive
Follow this blog board to get notified when there's new activity