Final Update: Thursday, 06 February 2020 00:30 UTC
We've confirmed that all systems are back to normal with no customer impact as of 02/05, 23:15 UTC. Our logs show the incident started on 02/05, 23:01 UTC and that during the 14 minutes that it took to resolve the issue some of customers experienced intermittent data latency , data gaps and incorrect alert activation in East US, South central US, East US2, North Central US regions.
-Subhash
We've confirmed that all systems are back to normal with no customer impact as of 02/05, 23:15 UTC. Our logs show the incident started on 02/05, 23:01 UTC and that during the 14 minutes that it took to resolve the issue some of customers experienced intermittent data latency , data gaps and incorrect alert activation in East US, South central US, East US2, North Central US regions.
- Root Cause: The failure was due to one of dependency service .
- Incident Timeline: 0 Hours & 14 minutes - 02/05, 23:01 UTC through 02/05, 23:15 UTC
-Subhash
Published Feb 06, 2020
Version 1.0