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 8, 2026

No incidents reported today.

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

May 5, 2026

Event storage cluster instability

Resolved - The indexation is back to real-time.

Thank you for you patience.
May 5, 17:23 UTC

Monitoring - The applied fix is working as exepected and we're now cathing the lag.
The incident is actively monitored.
We will continue to inform you on the progress.
May 5, 16:14 UTC

Identified - We applied a fix and indexation has now resumed.
We're now starting to catch the lag.
The incident is actively monitored for stability.
May 5, 16:02 UTC

Investigating - We identified a network issue on event storage cluster which cause searches and indexation instability.
We already recovered cold data, restoring search query functionality to include all events.
However, we're still experiencing indexation issues which are under investigation.
We're working on fix the issue, and further updates will be provided as necessary.
May 5, 15:21 UTC

May 4, 2026

No incidents reported.

May 3, 2026

No incidents reported.

May 2, 2026

No incidents reported.

May 1, 2026

No incidents reported.

Apr 30, 2026

No incidents reported.

Apr 29, 2026

No incidents reported.

Apr 28, 2026

No incidents reported.

Apr 27, 2026

Slowness on webapp

Resolved - Response time were back to normal at 11:25 CEST and are stable since.
This incident is over.
Thank you for your patience.
Apr 27, 11:55 UTC

Monitoring - We are currently experiencing slowness on some pages due to one of our components being overloaded.
A fix has been applied by our team and performances are coming back up.
We are still investigating on the root cause and working on improving performances and latency.

We will keep you updated
Apr 27, 09:32 UTC

Apr 26, 2026

No incidents reported.

Apr 25, 2026

Event indexation delay

Resolved - All missed events were correctly pushed to our storage engine during the night.
This incident is now over.
Thank you for your patience throughout this incident.
Apr 25, 08:50 UTC

Monitoring - The fix has been deployed and missed events are currently being indexed into our storage engine.

We will continue to inform you on the progress.
Apr 24, 18:16 UTC

Update - Our team is currently deploying a fix in order to index the missed events into the storage engine.

Be aware that the process is expected to cause duplicates of some events that were already pushed.

Thanks for your patience.
Apr 24, 16:58 UTC

Identified - Today at 12:38 CEST, we have started to progressively deploy our detection engine. Unfortunately, due to a misconfiguration, some events were not indexed into our storage engine, but all events were processed and related alerts were raised. The proportion of non-indexed events increased gradually. This issue was identified at 16:40 CEST and a fix was deployed around 17:00 CEST.

We are now working to fix the situation and ensure that all missed events will be correctly pushed to the storage engine.

During the issue, the detection engines continued to work as expected and alerts (including their related events) were correctly raised. All events related to alerts were also correctly indexed into our storage engine.
Apr 24, 15:59 UTC

Apr 24, 2026