SEKOIA FRA1 Status

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

Past Incidents

May 20, 2026

No incidents reported today.

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.

May 14, 2026

No incidents reported.

May 13, 2026

No incidents reported.

May 12, 2026

Ingestion degraded

Resolved - We are back to real-time indexing.
Thank you for your patience
May 12, 17:06 UTC

Monitoring - We applied a fix and are monitoring the region which is catching the lag on events ingestion.
May 12, 14:33 UTC

Update - We are continuing to work on a fix for this issue.
May 12, 10:22 UTC

Identified - Ingestion is slowly recovering. Additional cluster nodes are being provisioned to improve resilience. Monitoring continues to ensure full restoration.
May 12, 09:57 UTC

Investigating - Since 10:43, ingestion services in FRA1 region are experiencing degradation due to the message bus. This issue causes delays and slowdowns in event processing. The engineering team is investigating to restore normal operation as soon as possible.
May 12, 09:32 UTC

May 11, 2026

No incidents reported.

May 10, 2026

No incidents reported.

May 9, 2026

No incidents reported.

May 8, 2026

No incidents reported.

May 7, 2026

No incidents reported.

May 6, 2026

[FRA1] Event storage indexation delays

Resolved - This incident has been resolved.
May 6, 20:27 UTC

Monitoring - Approximately 32 servers became unresponsive due to high memory usage caused by a malfunction in the ingestion workflow components. A bulk hard reboot of affected servers has been initiated. Customers may experience delays and the ingestion of some events twice during this incident. There is no impact on automation features or playbooks. The situation is now stable and the backlog of events is being processed.
May 6, 14:30 UTC

Identified - The issue has been identified and a fix is being implemented.
May 6, 14:11 UTC

Investigating - We are experiencing configuration issues affecting multiple communities which are causing delays in event data indexing. Our teams are actively working to resolve the problem and restore normal indexing speed. Updates will be provided as the situation evolves.
May 6, 10:19 UTC