Final Update: Monday, 21 February 2022 13:12 UTC
We've confirmed that all systems are back to normal with no customer impact as of 02/21, 12:08 UTC. Our logs show the incident started on 02/21, 11:38 UTC and that during the 30 minutes that it took to resolve the issue some of the customers ingesting telemetry in China east region may have experienced intermittent data latency, data gaps and incorrect alert activation.
-Soumyajeet
We've confirmed that all systems are back to normal with no customer impact as of 02/21, 12:08 UTC. Our logs show the incident started on 02/21, 11:38 UTC and that during the 30 minutes that it took to resolve the issue some of the customers ingesting telemetry in China east region may have experienced intermittent data latency, data gaps and incorrect alert activation.
- Root Cause: The failure was due to one of our backend dependent service becoming unhealthy.
- Incident Timeline: 30 minutes - 02/21, 11:38 UTC through 02/21, 12:08 UTC
-Soumyajeet
