Final Update: Friday, 02 October 2020 05:41 UTC
We've confirmed that all systems are back to normal with no customer impact as of 10/02, 05:15 UTC. Our logs show the incident started on 10/02, 04:05 UTC and that during the 1 Hours & 10 minutes that it took to resolve, some customers may have experienced intermittent data latency and incorrect alert activation in Japan East Region.
-Vamshi
We've confirmed that all systems are back to normal with no customer impact as of 10/02, 05:15 UTC. Our logs show the incident started on 10/02, 04:05 UTC and that during the 1 Hours & 10 minutes that it took to resolve, some customers may have experienced intermittent data latency and incorrect alert activation in Japan East Region.
- Root Cause: The failure is due to configuration issues with one of our dependent service.
- Incident Timeline: 1 Hours & 10 minutes - 10/02, 04:05 UTC through 10/02, 05:15 UTC.
-Vamshi
Updated Oct 02, 2020
Version 3.0