Final Update: Monday, 29 April 2019 11:03 UTC
We've confirmed that all systems are back to normal with no customer impact as of 04/29, 10:45 UTC. Our logs show the incident started on 04/29, 08:20 UTC and that during the 2 hours 25 minutes that it took to resolve the issue, Customers must have experienced Alerting failures for the alerts configured in the Australia - South East Region.
-Monish
We've confirmed that all systems are back to normal with no customer impact as of 04/29, 10:45 UTC. Our logs show the incident started on 04/29, 08:20 UTC and that during the 2 hours 25 minutes that it took to resolve the issue, Customers must have experienced Alerting failures for the alerts configured in the Australia - South East Region.
- Root Cause: The failure was due to the issues in one of our dependent services.
- Incident Timeline: 2 hours 25 minutes - 04/29, 04/29, 08:20 UTC through 04/29, 10:45 UTC
-Monish
Initial Update: Monday, 29 April 2019 10:34 UTC
We are aware of issues within Log Search Alerts and are actively investigating. Customers may experience Alerting failures for the Alerts configured in the Australia - South East Region.
-Monish
We are aware of issues within Log Search Alerts and are actively investigating. Customers may experience Alerting failures for the Alerts configured in the Australia - South East Region.
- Work Around: None
- Next Update: Before 04/29 14:00 UTC
-Monish
Updated Apr 29, 2019
Version 3.0