Final Update: Sunday, 09 February 2020 15:00 UTC
We've confirmed that all systems are back to normal with no customer impact as of 2/9, 14:30 UTC. Our logs show the incident started on 2/9, 13:00 UTC and that during the 1 hour and 30 minutes that it took to resolve the issue customers using Log Search Alerts may have experienced delayed or missing Log Search Alerts in East Asia region.
We've confirmed that all systems are back to normal with no customer impact as of 2/9, 14:30 UTC. Our logs show the incident started on 2/9, 13:00 UTC and that during the 1 hour and 30 minutes that it took to resolve the issue customers using Log Search Alerts may have experienced delayed or missing Log Search Alerts in East Asia region.
- Root Cause: The failure was due to issue with one of our backend service.
- Incident Timeline: 1 Hour & 30 minutes - 2/9, 13:00 UTC through 2/9, 14:30 UTC
-Rama
Updated Feb 09, 2020
Version 2.0