Final Update: Saturday, 05 June 2021 03:06 UTC
We've confirmed that all systems are back to normal with no customer impact as of 6/5, 02:45 UTC. Our logs show the incident started on 6/5, 00:25 UTC and that during the two hours and twenty minutes that it took to resolve the issue approximately 4000 customers may have experienced data latency, data loss and latent or misfired alerts.
-Jack
We've confirmed that all systems are back to normal with no customer impact as of 6/5, 02:45 UTC. Our logs show the incident started on 6/5, 00:25 UTC and that during the two hours and twenty minutes that it took to resolve the issue approximately 4000 customers may have experienced data latency, data loss and latent or misfired alerts.
- Root Cause: The failure was due to faulty configuration of a backend service.
- Incident Timeline: 2 Hours & 20 minutes - 6/5, 00:25 UTC through 6/5, 02:45 UTC
-Jack
Initial Update: Saturday, 05 June 2021 02:39 UTC
We are aware of issues within Application Insights data ingestion in the East Japan region and are actively investigating. Some customers may experience delayed or missed Log Search Alerts and Latency and Data Loss.
-Jack
We are aware of issues within Application Insights data ingestion in the East Japan region and are actively investigating. Some customers may experience delayed or missed Log Search Alerts and Latency and Data Loss.
- Next Update: Before 06/05 04:00 UTC
-Jack
Updated Jun 05, 2021
Version 2.0