SEKOIA.IO Status

All Systems Operational

FRA1 - XDR Operational

Ingestion Operational

Threat Intelligence for research & triage Operational

Automation Operational

Event storage Operational

Detection Operational

Hunting Operational

Case management Operational

Web application Operational

FRA1 - CTI Operational

Search Operational

API consumption Operational

TAXII consumption Operational

MISP consumption Operational

Enrichers Operational

Web application Operational

FRA2 - XDR (SecNumCloud / PCI DSS region) Operational

MCO1 - XDR Operational

EUR1 - XDR Operational

UAE1 - XDR Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Oct 23, 2024

No incidents reported today.

Oct 22, 2024

Event ingestion delays

Resolved - All backlog has been processed, this incident is now over.
Oct 22, 23:40 CEST

Monitoring - We managed to identify the issue and process the backlog of pending tasks on the cluster responsible for event ingestion. We are now catching up on the backlog of enqueued events.
Oct 22, 21:33 CEST

Update - Investigation is still ongoing.
Oct 22, 20:21 CEST

Investigating - We are currently experiencing performance issues with event ingestion. As a results, events may show up late into the events page.
Our team is looking into this issue.
Oct 22, 18:48 CEST

Oct 21, 2024

No incidents reported.

Oct 20, 2024

No incidents reported.

Oct 19, 2024

No incidents reported.

Oct 18, 2024

No incidents reported.

Oct 17, 2024

FRA1 detection is down

Resolved - This incident has been resolved.
All alerts are being processed in real time.
Oct 17, 16:32 CEST

Monitoring - We are pleased to inform you that the fix has been successfully deployed. No alerts were lost during this incident. However please note that some alerts may experience some temporary delay. Our team is closely monitoring the situation to ensure everything returns to normal promptly. Thank you for your patience and support.
Oct 17, 16:10 CEST

Identified - We have identified an issue with our detection engine and have temporarily paused it to prevent any false alerts.
Rest assured, our team is actively working on a solution, which we expect to deploy shortly.
Thank you for your patience and understanding.
Oct 17, 15:50 CEST

Temporary Disruption in "Alert Created" Playbook Triggers

Resolved - On 17/10, at 16:54 CEST, a deployment introduced a bug into production which led to the "alert created" playbook triggers not being activated. All other triggers and playbooks continued to operate without any issues.

Our team detected the issue and has already rolled back the affected deployment as of 10:09 today. We are actively working on replaying the missed triggers and are developing a permanent fix to prevent similar incidents in the future.

We apologize for any inconvenience caused and appreciate your patience while we resolve this matter.

Thank you for your understanding.
Oct 17, 05:00 CEST

Oct 16, 2024

No incidents reported.

Oct 15, 2024

No incidents reported.

Oct 14, 2024

No incidents reported.

Oct 13, 2024

No incidents reported.

Oct 12, 2024

No incidents reported.

Oct 11, 2024

No incidents reported.

Oct 10, 2024

No incidents reported.

Oct 9, 2024

Bug in the Microsoft 365 Defender format update

Resolved - Today at 11:16 CEST, an issue with an unexpected surge in alerts arose, which has since been resolved. This was linked to a recent update in the Microsoft 365 Defender format, which included relocating certain process information to process.parent for AdvancedHunting-DeviceEvents and AdvancedHunting-DeviceProcessEvents.

Resolution Summary:

- The Microsoft Defender for Endpoint integration was reverted to its previous version to stop potentially false positive alerts.
- We are addressing and dismissing non-relevant alerts that were raised.

Thank you for your understanding and patience. The incident is now fully resolved.
Oct 9, 11:30 CEST