Sekoia FRA1 Outage History

Started Aug 03, 2026, 10:22 AM UTC· resolved Aug 03, 2026, 12:11 PM UTC

1. investigating Aug 03, 2026, 10:22 AM UTC

   Ongoing incident in FRA1 impacting notebook query functionality. Users may experience failures when running notebooks.

2. monitoring Aug 03, 2026, 10:50 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Aug 03, 2026, 12:11 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 27, 2026, 07:50 AM UTC· resolved Jul 28, 2026, 05:09 PM UTC

1. investigating Jul 27, 2026, 07:50 AM UTC

   An unexpected cloud provider maintenance is currently affecting our Playbooks automations services. Our engineering team is currently investigating the issue and trying to restore services in a timely manner. We thank you for your patience during resolution.

2. investigating Jul 27, 2026, 09:22 AM UTC

   We are experiencing an outage caused by an unexpected infrastructure restart. We are pushing our Cloud Provider for immediate resolution to bypass the provider's standard recovery timeframe. We will keep you informed

3. identified Jul 27, 2026, 10:39 AM UTC

   We are still pending the restart completion for impacted component infrastructure which is currently impacting our Playbooks functionality. Our engineering team is in permanent contact with cloud provider teams to ensure the restart is performed in a timely manner. We thank you for your patience during resolution.

4. identified Jul 27, 2026, 02:36 PM UTC

   We are continuing to work on a fix for this issue.

5. identified Jul 27, 2026, 02:39 PM UTC

   Despite cloud provider rollover, the affected resources are still unavailable, and the Playbooks functionality are still heavily impacted. Our engineering teams are still in direct contact with Cloud provider to recover the situation as soon as possible. We thank you for your patience during the resolution of this incident.

6. identified Jul 27, 2026, 06:13 PM UTC

   Following an underlying cloud provider issue, we are required to rebuild part of our Playbook infrastructure. Our engineering team is fully focused on re-deploying the environment as quickly and safely as possible.

7. monitoring Jul 28, 2026, 06:13 AM UTC

   Our Engineering team has been fully mobilized overnight to rebuild our Playbook infrastructure. Playbooks are now fully available. Our team is now focused on replaying actions and triggers impacted by the incident. We thank you again for your demonstrated patience during the resolution of this incident

8. monitoring Jul 28, 2026, 10:36 AM UTC

   Actions and triggers impacted by the incident are being replayed. Our engineering team is monitoring closely the situation, and current estimation provides a completion ETA by 1.30 pm CET for the replay to complete. During the incident, some users faced issues with triggers unable to start and remaining in inconsistent state. Those triggers have been stopped, and can now be restarted manually by users. A final update will be provided when replay operations are complete.

9. resolved Jul 28, 2026, 05:09 PM UTC

   The incident has been resolved, we are back to real-time processing, and everything is stable.

Read the full incident report →

Started Jul 13, 2026, 08:00 PM UTC· resolved Jul 14, 2026, 12:22 AM UTC

1. identified Jul 13, 2026, 08:00 PM UTC

   Our platform is experiencing delays with indexation and detection. The engineering team is fully mobilized to restore real-time indexation and detection in shortest timeframe. We thank you for your patience during resolution.

2. resolved Jul 14, 2026, 12:22 AM UTC

   We are back to real-time processing, and everything is stable. Thank you for your patience throughout this incident.

Read the full incident report →

Started Jul 12, 2026, 08:29 AM UTC· resolved Jul 12, 2026, 12:12 PM UTC

1. investigating Jul 12, 2026, 08:29 AM UTC

   We are currently experiencing an incident impacting a large part of our services. It causes lag in event processing/alert-raising/indexing, and API errors on multiple services. Our teams are investigating with our cloud-provider to find the root cause and a solution. Thank you for your patience.

2. identified Jul 12, 2026, 10:12 AM UTC

   We identified network component culprit and proceeding to restore services. Thank you for your patience.

3. monitoring Jul 12, 2026, 10:19 AM UTC

   All services are back to normal There is still a little delay on the ingestion chain but it's resolving fast and will be caught up in a matter of minutes Our teams are monitoring the resolution and we will be able to close this incident as soon as everything is back to real-time processing Thank you for your patience

4. resolved Jul 12, 2026, 12:12 PM UTC

   We are back to real-time processing and everything is stable. Thank you for your patience throughout this incident.

Read the full incident report →

Started Jun 26, 2026, 08:45 AM UTC· resolved Jun 26, 2026, 09:05 AM UTC

1. investigating Jun 26, 2026, 08:45 AM UTC

   We are experiencing issue on event search, impacting some customers. We are investigating the root cause. Thank you for your patience.

2. identified Jun 26, 2026, 08:55 AM UTC

   We identified the issue, the event search is operational, you may experience some lag on search Job. Thank you for your patience.

3. monitoring Jun 26, 2026, 08:58 AM UTC

   We are now monitoring the situation

4. resolved Jun 26, 2026, 09:05 AM UTC

   All systems are now operational Thank you for your patience.

Read the full incident report →

Started Jun 03, 2026, 03:10 PM UTC· resolved Jun 04, 2026, 06:15 PM UTC

1. investigating Jun 03, 2026, 03:10 PM UTC

   An ongoing incident is currently impacting event indexing and searches for some customers. Engineers are investigating on the issue.

2. identified Jun 03, 2026, 03:11 PM UTC

   An ongoing incident in the FRA1 region is impacting event indexing and search capabilities for some customers. The event storage is experiencing some failures which causes unstabilities, this results in delayed ingestion and unavailable searches. Engineers are investigating and working on mitigations to restore indexing and search functionality.

3. monitoring Jun 03, 2026, 05:41 PM UTC

   The underlying infrastructure have been stabilized and indexing has resumed, we're currently catching event indexing lag.

4. resolved Jun 04, 2026, 08:58 AM UTC

   This incident has been resolved. All events are being indexed in real time and available for searches.

Read the full incident report →

Started Jun 01, 2026, 10:24 AM UTC· resolved Jun 01, 2026, 05:11 PM UTC

1. identified Jun 01, 2026, 10:24 AM UTC

   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.

2. monitoring Jun 01, 2026, 10:32 AM UTC

   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.

3. resolved Jun 01, 2026, 05:11 PM UTC

   Backlog has been processed since 18:40 CEST and systems are stable. Thank you for your patience

Read the full incident report →

Started May 29, 2026, 05:57 PM UTC· resolved May 29, 2026, 11:09 PM UTC

1. investigating May 29, 2026, 05:57 PM UTC

   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.

2. identified May 29, 2026, 07:12 PM UTC

   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.

3. monitoring May 29, 2026, 07:50 PM UTC

   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.

4. resolved May 29, 2026, 11:09 PM UTC

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

Read the full incident report →

Started May 28, 2026, 07:36 AM UTC· resolved May 28, 2026, 01:03 PM UTC

1. investigating May 28, 2026, 07:36 AM UTC

   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.

2. identified May 28, 2026, 09:24 AM UTC

   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.

3. monitoring May 28, 2026, 09:37 AM UTC

   Teams continue to work on completing the backlog

4. resolved May 28, 2026, 01:03 PM UTC

   All the backlog has been processed Thanks for you patience

Read the full incident report →

Started May 20, 2026, 12:53 PM UTC· resolved May 20, 2026, 09:45 PM UTC

1. investigating May 20, 2026, 12:53 PM UTC

   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.

2. identified May 20, 2026, 01:23 PM UTC

   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.

3. monitoring May 20, 2026, 04:34 PM UTC

   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.

4. resolved May 20, 2026, 09:45 PM UTC

   The backlog of tasks has been processed and the automation feature is fully restored.

Read the full incident report →

Started May 18, 2026, 07:40 AM UTC· resolved May 18, 2026, 10:31 AM UTC

1. investigating May 18, 2026, 07:40 AM UTC

   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.

2. identified May 18, 2026, 08:05 AM UTC

   We have identified the root cause of the issue and a fix is being applied.

3. monitoring May 18, 2026, 08:29 AM UTC

   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.

4. resolved May 18, 2026, 10:31 AM UTC

   Indexing is back to real-time processing for every community. This incident is now over. Thank you for your patience.

Read the full incident report →

Started May 17, 2026, 07:31 AM UTC· resolved May 17, 2026, 10:28 AM UTC

1. investigating May 17, 2026, 07:31 AM UTC

   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.

2. monitoring May 17, 2026, 09:13 AM UTC

   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.

3. resolved May 17, 2026, 10:28 AM UTC

   The issue with Exalog indexing and ingestion has been fully resolved. All systems have been operating normally since 11:30 CEST. Thank you for your patience.

Read the full incident report →

Started May 16, 2026, 07:52 AM UTC· resolved May 16, 2026, 11:49 AM UTC

1. investigating May 16, 2026, 07:52 AM UTC

   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.

2. identified May 16, 2026, 08:38 AM UTC

   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.

3. identified May 16, 2026, 08:43 AM UTC

   We are continuing to work on a fix for this issue.

4. monitoring May 16, 2026, 09:39 AM UTC

   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.

5. monitoring May 16, 2026, 10:00 AM UTC

   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.

6. resolved May 16, 2026, 11:49 AM UTC

   All failed playbooks have been replayed. Thank you for your patience throughout this incident.

Read the full incident report →

Started May 12, 2026, 09:32 AM UTC· resolved May 12, 2026, 05:06 PM UTC

1. investigating May 12, 2026, 09:32 AM UTC

   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.

2. identified May 12, 2026, 09:57 AM UTC

   Ingestion is slowly recovering. Additional cluster nodes are being provisioned to improve resilience. Monitoring continues to ensure full restoration.

3. identified May 12, 2026, 10:22 AM UTC

   We are continuing to work on a fix for this issue.

4. monitoring May 12, 2026, 02:33 PM UTC

   We applied a fix and are monitoring the region which is catching the lag on events ingestion.

5. resolved May 12, 2026, 05:06 PM UTC

   We are back to real-time indexing. Thank you for your patience

Read the full incident report →

Started May 06, 2026, 10:19 AM UTC· resolved May 06, 2026, 08:27 PM UTC

1. investigating May 06, 2026, 10:19 AM UTC

   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.

2. identified May 06, 2026, 02:11 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring May 06, 2026, 02:30 PM UTC

   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.

4. resolved May 06, 2026, 08:27 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 05, 2026, 03:21 PM UTC· resolved May 05, 2026, 05:23 PM UTC

1. investigating May 05, 2026, 03:21 PM UTC

   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.

2. identified May 05, 2026, 04:02 PM UTC

   We applied a fix and indexation has now resumed. We're now starting to catch the lag. The incident is actively monitored for stability.

3. monitoring May 05, 2026, 04:14 PM UTC

   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.

4. resolved May 05, 2026, 05:23 PM UTC

   The indexation is back to real-time. Thank you for you patience.

Read the full incident report →

Started Apr 27, 2026, 09:32 AM UTC· resolved Apr 27, 2026, 11:55 AM UTC

1. monitoring Apr 27, 2026, 09:32 AM UTC

   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

2. resolved Apr 27, 2026, 11:55 AM UTC

   Response time were back to normal at 11:25 CEST and are stable since. This incident is over. Thank you for your patience.

Read the full incident report →

Started Apr 24, 2026, 03:59 PM UTC· resolved Apr 25, 2026, 08:50 AM UTC

1. identified Apr 24, 2026, 03:59 PM UTC

   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.

2. identified Apr 24, 2026, 04:58 PM UTC

   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.

3. monitoring Apr 24, 2026, 06:16 PM UTC

   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.

4. resolved Apr 25, 2026, 08:50 AM UTC

   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.

Read the full incident report →

Started Apr 15, 2026, 07:57 AM UTC· resolved Apr 15, 2026, 04:46 PM UTC

1. investigating Apr 15, 2026, 07:57 AM UTC

   We are currently experiencing an incident impacting the playbook automation feature. The team is actively investigating the root cause and working on remediation.

2. identified Apr 15, 2026, 08:34 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Apr 15, 2026, 12:08 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Apr 15, 2026, 04:46 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 08, 2026, 09:15 AM UTC· resolved Apr 08, 2026, 12:07 PM UTC

1. investigating Apr 08, 2026, 08:58 AM UTC

   We are currently investigating an issue affecting Assets availability on the platform. Our Engineering team is fully mobilized to resolve the issue.

2. monitoring Apr 08, 2026, 09:15 AM UTC

   The issue has been identified and the assets functionalities are back up, and available through the web application and APIs. Stabilization actions are ongoing which should not further impact users

3. monitoring Apr 08, 2026, 09:15 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Apr 08, 2026, 12:07 PM UTC

   All assets functionality have been resolved and recovery actions completed. Thank you for your patience during resolution

Read the full incident report →

Started Apr 04, 2026, 09:00 PM UTC· resolved Apr 04, 2026, 10:50 PM UTC

1. investigating Apr 04, 2026, 09:00 PM UTC

   We are currently investigating degraded ingestion performance. Our teams are actively working to identify the cause and restore normal performance as quickly as possible. We will share another update as soon as more information is available.

2. monitoring Apr 04, 2026, 09:26 PM UTC

   We have identified and fixed the issue affecting ingestion. Ingestion is now operating normally again. Some delay may still be visible while the remaining lag is being processed, and we expect the situation to be fully back to normal soon. We are continuing to monitor the recovery closely.

3. resolved Apr 04, 2026, 10:50 PM UTC

   The issue affecting ingestion has been resolved. Ingestion performance is back to normal, and the temporary lag has been fully absorbed. We will continue to monitor the platform, but the incident is now closed.

Read the full incident report →

Started Mar 20, 2026, 08:25 AM UTC· resolved Mar 23, 2026, 08:13 AM UTC

1. identified Mar 20, 2026, 08:25 AM UTC

   We are currently experiencing an incident affecting task execution due to a limitation in the cluster responsible for coordination and scheduling. This issue started yesterday around 18:26 and has prevented new processing tasks from starting. The engineering team has identified the root cause to mitigate the issue. Investigation and remediation efforts are ongoing.

2. monitoring Mar 20, 2026, 09:05 AM UTC

   Pod scheduling and task execution have resumed following administrative actions on the cluster. The situation is currently being monitored.

3. monitoring Mar 20, 2026, 03:56 PM UTC

   We are currently replaying the pending tasks and monitoring system stability.

4. resolved Mar 23, 2026, 08:13 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 06, 2026, 10:54 AM UTC· resolved Mar 06, 2026, 03:52 PM UTC

1. identified Mar 06, 2026, 10:54 AM UTC

   Following a maintenance operation on a shared event storage cluster node, observables are currently unavailable, impacting alert generation and sightings across all regions. This results in alerts not being raised, affecting the product's visibility on security events.

2. monitoring Mar 06, 2026, 10:59 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Mar 06, 2026, 03:52 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 26, 2026, 03:09 PM UTC· resolved Feb 26, 2026, 06:45 PM UTC

1. identified Feb 26, 2026, 03:09 PM UTC

   The indexation service in the FRA1 region is currently degraded due to multiple nodes going down in the event storage cluster caused by a hardware outage on our cloud provider. The incident started around 15:00 and prevents writing to several indices. Operations teams are performing recovery operations on the affected indices to restore service.

2. monitoring Feb 26, 2026, 03:22 PM UTC

   The indexation service in the FRA1 region has been restored following a hardware outage at the cloud provider affecting multiple nodes in the event storage cluster. Recovery operations on affected indices have been completed. Monitoring continues to ensure stability and recovery.

3. resolved Feb 26, 2026, 06:45 PM UTC

   Recovery has been completed, and backlogged events have been fully processed. We thank you for your patience during the resolution.

Read the full incident report →

Started Feb 26, 2026, 10:40 AM UTC· resolved Feb 26, 2026, 10:59 AM UTC

1. investigating Feb 26, 2026, 10:40 AM UTC

   Some API endpoints are returning 500 errors intermittently. Our engineering team is currently investigating the issue. We thank you for your patience during the resolution.

2. identified Feb 26, 2026, 10:57 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Feb 26, 2026, 10:57 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Feb 26, 2026, 10:59 AM UTC

   This incident has been resolved.

Read the full incident report →