This incident is resolved and playbooks and automation features in FRA1 are stable. Some playbooks that failed during the incident are being re-run and should complete within a few minutes. We apologize for the inconvenience.
Posted Nov 06, 2026 - 15:56 UTC
Monitoring
Playbooks, intake connectors and automation features in FRA1 appear to be back to normal. Some delay may still be noticeable while our system catches up, which will take some time.
We are closely monitoring the situation to confirm that it remains stable.
Posted Nov 06, 2026 - 15:06 UTC
Update
We have identified a likely network-related cause for the delays affecting playbooks, intake connectors and automation features in FRA1. Our teams are currently applying a corrective change.
We will post an update within 30 minutes or sooner if the situation changes.
Posted Nov 06, 2026 - 14:41 UTC
Update
The situation has not changed since our last update, and execution times are not yet back to normal. Our teams are continuing their work.
Posted Nov 06, 2026 - 14:11 UTC
Update
The situation has not changed since our last update, and execution times are not yet back to normal. Our teams are continuing their work.
We will post an update within 30 minutes or sooner if the situation changes.
Posted Nov 06, 2026 - 13:44 UTC
Update
The situation has slightly improved following corrective actions, but execution times are not yet back to normal. Our teams are continuing their work.
We will post an update within 30 minutes or sooner if the situation changes.
Posted Nov 06, 2026 - 13:16 UTC
Update
We have identified the cause of the delays affecting playbooks and automation features in FRA1. Our teams are now working on the corrective action to restore normal execution times.
We will post an update within 30 minutes or sooner if the situation changes.
Posted Nov 06, 2026 - 13:02 UTC
Identified
We are aware that automated response workflows in FRA1 are currently experiencing delays. Users may notice that playbooks are taking longer than expected to execute.
Our engineering team is actively investigating the root cause. We will post an update within 30 minutes or sooner if the situation changes.