Final Update: Tuesday, 16 June 2020 21:16 UTC
We've confirmed that all systems are back to normal with no customer impact as of 06/16, 20:10 UTC. Our logs show the incident started on 06/16, 19:45 UTC and that during the 25 minutes that it took to resolve small set of customers in East US have experienced issues with Activity Log Alerts not being fired.
-
Root Cause: The failure was due to one of dependent service
-
Incident Timeline: 0 Hours & 25 minutes - 06/16, 19:45 UTC through 06/16, 20:10 UTC
We understand that customers rely on Activity Log Alerts as a critical service and apologize for any impact this incident caused.
-Subhash