Final Update: Saturday, 12 June 2021 21:34 UTC
Updating title to reflect status change.
-Chandar.
Final Update: Saturday, 12 June 2021 20:59 UTC
We've confirmed that all systems are back to normal with no customer impact as of 06/12, 20:30 UTC. Our logs show the incident started on 06/12, 17:45 UTC and that during the time that it took to resolve the issue 1.1% of Activity Log Alerts customers in Europe region may not have been able to edit or view existing rules.
-
Root Cause: The failure was due to front nodes that processing incoming requests failed with errors.
- Incident Timeline: 06/12, 17:45 UTC through 06/12, 20:30 UTC
We understand that customers rely on Activity Log Alerts as a critical service and apologize for any impact this incident caused.
-chandar
Update: Saturday, 12 June 2021 20:35 UTC
We continue to investigate issues within Activity Log Alerts. Root cause is not fully understood at this time. Some customers continue to experience difficulties to view or edit existing alert rules. We are working to establish the start time for the issue, initial findings indicate that the problem began at 06/12 17:45 UTC. We currently have no estimate for resolution.
- Work Around:
- Next Update: Before 06/12 22:00 UTC
-chandar
Initial Update: Saturday, 12 June 2021 20:27 UTC
We are aware of issues within Activity Log Alerts and are actively investigating. Activity Log alerts customers in the Europe region would not be able view or update existing rules.
- Work Around:
- Next Update: Before 06/12 21:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Chandar
