Final Update: Friday, 20 March 2020 20:27 UTC
We've confirmed that all systems are back to normal with no customer impact as of 03/20, 19:40 UTC. Our logs show the incident started on 03/20, 11:35 UTC and that during the 8 hours and 5 minutes that it took to resolve the issue customers in the US Gov Regions may have experienced delayed or missed alerts.
-
Root Cause: The failure was due to an incorrect configuration on a dependent backend service.
-
Incident Timeline: 8 Hours & 5 minutes - 03/20, 11:35 UTC through 03/20, 19:40 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.
-Eric Singleton