Final Update: Wednesday, 29 July 2020 12:27 UTC
We've confirmed that all systems are back to normal with no customer impact as of 7/29, 11:10 UTC. Our logs show the incident started on 7/29, 09:05 UTC and that during the 2 hours and 5 minutes that it took to resolve the issue some customers in West Central US region may have experienced issues with missed or delayed log search alerts.
-Madhuri
We've confirmed that all systems are back to normal with no customer impact as of 7/29, 11:10 UTC. Our logs show the incident started on 7/29, 09:05 UTC and that during the 2 hours and 5 minutes that it took to resolve the issue some customers in West Central US region may have experienced issues with missed or delayed log search alerts.
- Root Cause: The failure was due to an issue in one of our dependent services.
- Incident Timeline: 2 Hours & 5 minutes - 7/29, 09:05 UTC through 7/29, 11:10 UTC
-Madhuri
Initial Update: Wednesday, 29 July 2020 11:26 UTC
We are aware of issues within Log Search Alerts and are actively investigating. Some customers in West Central US may experience issues with missed or delayed log search alerts.
-Madhuri
We are aware of issues within Log Search Alerts and are actively investigating. Some customers in West Central US may experience issues with missed or delayed log search alerts.
- Work Around: None.
- Next Update: Before 07/29 13:30 UTC
-Madhuri
Updated Jul 29, 2020
Version 2.0