All Systems Operational

Web application Operational
Event ingestion Operational
Event storage Operational
Detection Operational
Hunting Operational
Case management Operational
Automation Operational
AI Operational
CTI Search Operational
CTI Feed (API) Operational
CTI Feed (TAXII) Operational
CTI Feed (MISP) Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
May 29, 2026

No incidents reported today.

May 28, 2026
Automation features unavailable
Resolved - All the backlog has been processed
Thanks for you patience
May 28, 13:03 UTC
Monitoring - Teams continue to work on completing the backlog
May 28, 09:37 UTC
Identified - Engineers identified and isolated the offending playbook and restored real-time processing.
A backlog playbook tasks remains and customers may see delayed automated workflows while the backlog is processed.
Teams continue to work on completing the backlog.
May 28, 09:24 UTC
Investigating - An ongoing incident is affecting automation features: playbook actions are not being triggered. Customers may experience failures of automated workflows. Engineering teams are investigating and working on a fix.
May 28, 07:36 UTC
May 27, 2026

No incidents reported.

May 26, 2026

No incidents reported.

May 25, 2026

No incidents reported.

May 24, 2026

No incidents reported.

May 23, 2026

No incidents reported.

May 22, 2026

No incidents reported.

May 21, 2026

No incidents reported.

May 20, 2026
Symphony playbook automation degraded
Resolved - The backlog of tasks has been processed and the automation feature is fully restored.
May 20, 21:45 UTC
Monitoring - The automation feature has been fully restored, with real-time processing resumed. We are currently handling the backlog of tasks which couldn't be handled in time.
May 20, 16:34 UTC
Identified - The major incident affecting automation features in the FRA1 cloud region is currently under recovery. The automation feature for playbooks runs was stopped to mitigate the issue and is now being restarted gradually. Customers may still experience delays in playbook runs, but recovery is in progress.
May 20, 13:23 UTC
Investigating - We are currently experiencing a major incident affecting the automation features in the FRA1 cloud region. An excessive number of automation playbook runs are being triggered overwhelming the system and causing no new playbook runs to be processed. We are investigating the issue.
May 20, 12:53 UTC
May 19, 2026

No incidents reported.

May 18, 2026
Partial indexing lag
Resolved - Indexing is back to real-time processing for every community.
This incident is now over. Thank you for your patience.
May 18, 10:31 UTC
Monitoring - We have applied a fix. We are currently monitoring the systems as they return to normal.
We will let you know as soon as the issue is fully resolved.
May 18, 08:29 UTC
Identified - We have identified the root cause of the issue and a fix is being applied.
May 18, 08:05 UTC
Investigating - We are currently investigating an indexing issue. This is causing processing lag to data ingestion only on few communities. Our engineering team is actively working to identify the root cause and mitigate the impact. We will provide an update shortly.
May 18, 07:40 UTC
May 17, 2026
Storage indexing lag
Resolved - The issue with our indexing and ingestion has been fully resolved. All systems have been operating normally since 11:30 CEST. Thank you for your patience.
May 17, 10:28 UTC
Monitoring - We have identified the root cause of the issue and applied a fix. We are currently monitoring the systems as they return to normal.
We will let you know as soon as the issue is fully resolved.
May 17, 09:13 UTC
Investigating - We are currently investigating an indexing issue specifically affecting Exalog. This is causing processing lag to data ingestion. Our engineering team is actively working to identify the root cause and mitigate the impact. We will provide an update shortly.
May 17, 07:31 UTC
May 16, 2026
FRA1 Event processing stopped
Resolved - All failed playbooks have been replayed.
Thank you for your patience throughout this incident.
May 16, 11:49 UTC
Update - We are currently re-running the playbooks that failed during the incident. Once these executions are complete, the incident will be marked as fully resolved.
May 16, 10:00 UTC
Monitoring - The backlog of safely queued events has been fully processed, and all systems (ingestion, search, and alerting) have returned to normal performance. We appreciate your patience and apologize for any inconvenience this disruption may have caused.
May 16, 09:39 UTC
Update - We are continuing to work on a fix for this issue.
May 16, 08:43 UTC
Identified - We have identified the root cause of the service disruption and applied a fix. Event ingestion, search, and alerting functionalities are now resuming. However, you may experience degraded performance and slower response times as our systems process the backlog of safely stored events.
May 16, 08:38 UTC
Investigating - We have been experiencing an issue affecting event search, alerting and processing. Users may encounter errors when trying to search or access events. Please be assured that our data reception systems are fully operational and no events are being lost. All incoming data is safely stored and will be processed as soon as the issue is resolved. Our engineering team is actively working on a fix.
May 16, 07:52 UTC
May 15, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage