Final Update: Wednesday, 18 March 2020 13:44 UTC
We've confirmed that all systems are back to normal with no customer impact as of 03/18, 09:51 UTC. Our logs show the incident started on 03/18, 13:25 UTC and that during the 3 hours and 34 minutes that it took to resolve the issue some customers may have experienced Ingestion Latency, Query Failure and missed alerts in multiple regions.
-Madhuri
We've confirmed that all systems are back to normal with no customer impact as of 03/18, 09:51 UTC. Our logs show the incident started on 03/18, 13:25 UTC and that during the 3 hours and 34 minutes that it took to resolve the issue some customers may have experienced Ingestion Latency, Query Failure and missed alerts in multiple regions.
- Root Cause: The failure was due to an issue in one of our dependent services.
- Incident Timeline: 3 Hours & 34 minutes - 03/18, 09:51 UTC through 03/18, 13:25 UTC
-Madhuri
Initial Update: Wednesday, 18 March 2020 11:17 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience Ingestion Latency, Query Failure and missed alerts in multiple regions.
-Madhuri
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience Ingestion Latency, Query Failure and missed alerts in multiple regions.
- Work Around: None.
- Next Update: Before 03/18 13:30 UTC
-Madhuri
Updated Mar 18, 2020
Version 2.0