Final Update: Tuesday, 05 April 2022 09:02 UTC
We've confirmed that all systems are back to normal with no customer impact as of 04/05, 08:30 UTC. Our logs show the incident started on 04/05, 04:20 UTC and that during the 4 hours and 10 minutes that it took to resolve the issue some of customers in North Central US region may have experienced intermittent log data gaps and incorrect alert activation and/or latency.
-Soumyajeet
We've confirmed that all systems are back to normal with no customer impact as of 04/05, 08:30 UTC. Our logs show the incident started on 04/05, 04:20 UTC and that during the 4 hours and 10 minutes that it took to resolve the issue some of customers in North Central US region may have experienced intermittent log data gaps and incorrect alert activation and/or latency.
- Root Cause: The failure was due to one of the backend dependent service becoming unhealthy.
- Incident Timeline: 4 Hours & 10 minutes - 04/05, 04:20 UTC through 04/05, 08:30 UTC
-Soumyajeet
