Final Update: Tuesday, 25 January 2022 07:17 UTC
We've confirmed that all systems are back to normal with no customer impact as of 01/25, 06:20 UTC. Our logs show the incident started on 01/25, 04:51 UTC and that during the 1 hour & 29 minutes that it took to resolve the issue Customers using Azure Monitor or Azure Sentinels in Japan East region may have experienced issues in accessing data as well as missed or delayed Log Search alerts.
-Sai Kumar
We've confirmed that all systems are back to normal with no customer impact as of 01/25, 06:20 UTC. Our logs show the incident started on 01/25, 04:51 UTC and that during the 1 hour & 29 minutes that it took to resolve the issue Customers using Azure Monitor or Azure Sentinels in Japan East region may have experienced issues in accessing data as well as missed or delayed Log Search alerts.
- Root Cause: The issue was due to a backend dependency service failure.
- Incident Timeline: 1 Hours & 29 minutes - 01/25, 04:51 UTC through 01/25, 06:20 UTC
-Sai Kumar
Update: Tuesday, 25 January 2022 06:12 UTC
We continue to investigate issues within Log Analytics. Initial investigation point to bad deployment on cluster. Some customers using Azure Monitor or Azure Sentinels in Japan East region may have experienced issues in accessing data as well as missed or delayed Log Search alerts. The problem began at 01/25 ~04:51 UTC. We currently have no estimate for resolution.
We continue to investigate issues within Log Analytics. Initial investigation point to bad deployment on cluster. Some customers using Azure Monitor or Azure Sentinels in Japan East region may have experienced issues in accessing data as well as missed or delayed Log Search alerts. The problem began at 01/25 ~04:51 UTC. We currently have no estimate for resolution.
- Work Around: NA
- Next Update: Before 01/25 12:30 UTC
Updated Jan 24, 2022
Version 2.0