Alerting failure for Log Search Alerts in EUS, EUS2 and WCUS - 11/01 - Resolved
Published Nov 01 2019 04:02 PM 1,354 Views
Final Update: Friday, 01 November 2019 23:36 UTC

We've confirmed that all systems are back to normal with no customer impact as of 11/1, 23:36 UTC. Our logs show the incident started on 11/1, 20:15 UTC and that during the 3 hours, 21 minutes that it took to resolve some customers experienced latency in Log Search Alerts in East US, West Central US and East US 2.
  • Root Cause: The failure was due to a cache connection failure, which resulted in an internal denial of service event.
  • Incident Timeline: 3 Hours & 21 minutes - 11/1, 20:15 through 11/1, 23:36 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Jack Cantwell

Initial Update: Friday, 01 November 2019 23:01 UTC

We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience latency in Log Search Alerts in the East US region.
  • Work Around: none at this time
  • Next Update: Before 11/02 00:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jack Cantwell

Version history
Last update:
‎Nov 01 2019 04:55 PM
Updated by: