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
Dec 2, 2024

No incidents reported today.

Dec 1, 2024

No incidents reported.

Nov 30, 2024

No incidents reported.

Nov 29, 2024

No incidents reported.

Nov 28, 2024
Resolved - The platform is running on real-time since 00:34 UTC+1
Nov 28, 09:41 CET
Monitoring - A fix has been implemented and the delay is now decreasing slowly.
We will keep monitoring this incident and will close this status page once we are back in real-time.

Nov 27, 18:16 CET
Identified - We are aware of an incident causing delay to accumulate on the platform.
It concerns event processing and alert raising, which are currently happening about 10 minutes after an event is received.
And also the event indexing in our storage cluster, which is currently happening around 30 minutes after an event is processed.

We have identified the cause and are working towards its resolution.

Nov 27, 17:33 CET
Nov 27, 2024
Completed - The scheduled maintenance has been completed.
Nov 27, 10:43 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 27, 10:00 CET
Scheduled - Dear Customer,

We are pleased to inform you of an important update to our sekoia.io services in the FRA1 region. On 27/11/2024, we will be enhancing our security infrastructure by deploying a new Web Application Firewall (WAF) through our partner, Akamai. This change will result in an adjustment to the DNS entries for our domains, api.sekoia.io and app.sekoia.io, which will now point to a CNAME on Akamai's infrastructure instead of a previous A record.

It is important to note that such DNS changes have been implemented successfully in the past without any reported issues. Our team has thoroughly planned this transition to ensure continued stability and security for your operations.

Please be reminded that implementing IP filtering based on the current DNS entries for these domains is not recommended. As DNS-based infrastructures evolve, filtering by IP could disrupt access to our services. As always, we are committed to maintaining maximum security and uninterrupted service for our users.

Should you have any questions or need further assistance, please do not hesitate to contact our support team.

Thank you for your continued trust in sekoia.io.

Nov 19, 10:15 CET
Nov 26, 2024
Resolved - The playbooks environment is stable and steady.
This incident is not resolved.

Nov 26, 18:55 CET
Monitoring - The playbook environment is back up and we are processing tasks as usual.
We are back in real-time, however the environment is handling a lot of charge at the moment.
We are monitoring closely until everything is stable and back to normal.

Nov 26, 18:09 CET
Identified - We implemented a fix to the network issue.
The cluster is coming back online on our side.
We are currently stabilizing the cluster after the fix, and validating that everything is working.

Nov 26, 17:32 CET
Investigating - We detected an incident concerning our playbook runs that impacts DNS resolution and runs processing.
Nov 26, 16:05 CET
Nov 25, 2024

No incidents reported.

Nov 24, 2024

No incidents reported.

Nov 23, 2024

No incidents reported.

Nov 22, 2024
Resolved - The delay has been completely resolved since 21h50 UTC, the incident is now completely resolved.
Nov 22, 23:10 CET
Monitoring - Some fix were implemented to increase our performance.
We are now able to catch the delay, slowly but steadily.
We will close this status page once the event storage is back on real-time.

Nov 22, 19:30 CET
Update - The incident is still ongoing.
We are actively continuing to search for its root cause.
Our team has added some resources to the storage cluster as a temporary workaround.
At this stage, performance is still below our expectations, and we continue to experience delays.
We estimate the delay to be around 1 hour and 45 minutes between the processing of an event and its entry into our storage cluster.

Nov 22, 17:02 CET
Investigating - We are currently having issues indexing events in our storage cluster.
This is generating delay before the events are available in the events and alerts pages.
The detection is not affected.

Nov 22, 14:24 CET
Nov 21, 2024

No incidents reported.

Nov 20, 2024
Resolved - Events are processed in real-time since 17:39 CET, everything is stable.
Nov 20, 18:27 CET
Monitoring - During a service update on the region, we encountered an issue with our event processing.
It has been stopped for around an hour, since 15:33.
We have fixed the issue and it is now consuming again, we are catching up on the delay.
We expect around 1h before coming back to real-time processing.

Nov 20, 16:41 CET
Resolved - This incident has been resolved.
Nov 20, 14:12 CET
Monitoring - A fix has been implemented and we are now catching up on the lag.
We will keep monitoring closely and keep this status page open until we have no more delay on events processing.

Nov 20, 11:09 CET
Investigating - We are investigating an issue with our events processing pipeline which has bad performance since 09:27 CET.
Events processing is taking lag, which impacts alerts raising.

Nov 20, 10:46 CET
Nov 19, 2024

No incidents reported.

Nov 18, 2024

No incidents reported.