Final Update: Thursday, 11 July 2019 05:06 UTC
We've confirmed that all systems are back to normal with no customer impact as of 07/11, 04:30 UTC. Our logs show the incident started on 07/11, 01:30 UTC and that during the 3 hours that it took to resolve the issue 80% of customers using Log alerts which are configured in East Japan region would have experienced latency in detecting log alerts and execution of Log Search queries might have timed out.
-Rama
We've confirmed that all systems are back to normal with no customer impact as of 07/11, 04:30 UTC. Our logs show the incident started on 07/11, 01:30 UTC and that during the 3 hours that it took to resolve the issue 80% of customers using Log alerts which are configured in East Japan region would have experienced latency in detecting log alerts and execution of Log Search queries might have timed out.
- Root Cause: The failure was due to issues with one of our backend services which went in to unhealthy state.
- Incident Timeline: 3 Hours - 07/11, 01:30 UTC through 07/11, 04:30 UTC
-Rama
Initial Update: Thursday, 11 July 2019 04:12 UTC
We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience Alerting failures and data latency issues.
We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience Alerting failures and data latency issues.
- Next Update: Before 07/11 07:30 UTC
-Leela
Updated Jul 11, 2019
Version 4.0