Monitoring - Detection workflows were unavailable due to a cluster of cache instances becoming unresponsive after a deployment. The workflows have been restarted and all services are back online; event processing may be delayed but recovery and catch-up are in progress.
Jun 01, 2026 - 10:32 UTC
Identified - An ongoing incident is impacting detection services due to a failure in cache instances. Engineers are performing restarts and recovery steps; service restoration is in progress but may take some time.
Jun 01, 2026 - 10:24 UTC
Web application Operational
Event ingestion Operational
Event storage Operational
Detection Degraded Performance
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
Jun 1, 2026

Unresolved incident: Workflow service degraded — cache cluster unreachable.

May 31, 2026

No incidents reported.

May 30, 2026

No incidents reported.

May 29, 2026
Resolved - Indexing is in real-time for all communities since 23:15 CEST.
Everything is stable.
Thank you for your patience throughout this incident.

May 29, 23:09 UTC
Monitoring - The patches have been applied by our engineering team, and the situation is stable again.
Accumulated logs are being processed. We will keep you updated once indexing is back to real time.
Thank you for your patience.

May 29, 19:50 UTC
Identified - The root cause has been identified, and our team is currently applying patches.
Event indexing was delayed for the impacted communities, which means some events may appear late on event pages.
Indexing is now running and processing the backlog. Search is available again.

We will keep you updated.

May 29, 19:12 UTC
Investigating - We are currently facing an issue on our event storage impacting only some customers, impacting indexation and researches.
Our engineering team is actively working on diagnosing the root cause and finding a solution.
Thank you for you patience.

May 29, 17:57 UTC
May 28, 2026
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
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
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