This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Thursday, 24 March 2022 02:35 UTC
We've confirmed that all systems are back to normal with no customer impact as of 3/24, 02:32 UTC. Our logs show the incident started on 3/23, 23:25 UTC and that during the 3 hours and 7 minutes that it took to resolve the issue customers may experience up to 2 hours of ingestion latency and missed or delayed Log Search Alerts in the West Europe region.
-Eric Singleton
We've confirmed that all systems are back to normal with no customer impact as of 3/24, 02:32 UTC. Our logs show the incident started on 3/23, 23:25 UTC and that during the 3 hours and 7 minutes that it took to resolve the issue customers may experience up to 2 hours of ingestion latency and missed or delayed Log Search Alerts in the West Europe region.
- Root Cause: The failure was due to an underlying dependency
- Incident Timeline: 3 Hours & 7 minutes - 3/23, 23:25 UTC through 3/24, 2:32 UTC
-Eric Singleton
Update: Thursday, 24 March 2022 01:33 UTC
Root cause has been isolated to an underlying dependency which is in the process of recovering. Customers may experience up to 2 hours of ingestion latency and missed or delayed Log Search Alerts in the West Europe region
Root cause has been isolated to an underlying dependency which is in the process of recovering. Customers may experience up to 2 hours of ingestion latency and missed or delayed Log Search Alerts in the West Europe region
- Work Around: None
- Next Update: Before 03/24 04:00 UTC