Final Update: Wednesday, 15 January 2020 18:33 UTC
We've confirmed that all systems are back to normal with no customer impact as of 1/15, 18:05 UTC. Our logs show the incident started on 1/15, 17:31 UTC and that during the 34 minutes that it took to resolve the issue 4.3% of customers experienced failed or timing out queries as well as temporary log ingestion delay and possible misfiring or not firing alerts.
-Jeff
We've confirmed that all systems are back to normal with no customer impact as of 1/15, 18:05 UTC. Our logs show the incident started on 1/15, 17:31 UTC and that during the 34 minutes that it took to resolve the issue 4.3% of customers experienced failed or timing out queries as well as temporary log ingestion delay and possible misfiring or not firing alerts.
- Root Cause: The failure was due to a back end component becoming unhealthy. The component was taken out of rotation and component health was restored.
- Incident Timeline: 34 minutes - 1/15, 17:31 UTC through 1/15, 18:05 UTC
-Jeff
Initial Update: Wednesday, 15 January 2020 18:07 UTC
We are aware of issues within Application Insights and are actively investigating. Some customers may experience Data Access Issues.
-Jeff
We are aware of issues within Application Insights and are actively investigating. Some customers may experience Data Access Issues.
- Next Update: Before 01/15 20:30 UTC
-Jeff
Updated Jan 15, 2020
Version 2.0