Final Update: Friday, 19 February 2021 21:28 UTC
We've confirmed that all systems are back to normal with no customer impact as of 02/19, 21:17 UTC. Our logs show the incident started on 02/19, 20:24 UTC and that during the 53 minutes that it took to resolve the issue customers would have received 503 errors resulting in Data latency and data gaps as well as misfired alerts as a result of the data latency and gaps.
-Jeff
We've confirmed that all systems are back to normal with no customer impact as of 02/19, 21:17 UTC. Our logs show the incident started on 02/19, 20:24 UTC and that during the 53 minutes that it took to resolve the issue customers would have received 503 errors resulting in Data latency and data gaps as well as misfired alerts as a result of the data latency and gaps.
- Root Cause: The failure was due to a backend component that became unhealthy.
- Incident Timeline: 53 minutes - 02/19, 20:24 UTC through 02/19, 21:17 UTC
-Jeff
Initial Update: Friday, 19 February 2021 21:06 UTC
We are aware of issues within Application Insights in Japan West region and are actively investigating. Some customers may experience delayed or missed Log Search Alerts and Data Latency.
-Jeff
We are aware of issues within Application Insights in Japan West region and are actively investigating. Some customers may experience delayed or missed Log Search Alerts and Data Latency.
- Work Around: None
- Next Update: Before 02/19 22:30 UTC
-Jeff
Updated Feb 19, 2021
Version 2.0