Sekoia MCO1 Outage History

Sekoia MCO1 had 5 outages in the last 2 years totaling 20h 9m of downtime — averaging 0.2 incidents per month.

There were 5 Sekoia MCO1 outages since July 18, 2025 totaling 20h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.mco1.sekoia.io

Minor March 6, 2026

shared event storage cluster maintenance impacts observables and alerts

Detected by Pingoru: Mar 06, 2026, 10:56 AM UTC
Resolved: Mar 06, 2026, 03:53 PM UTC
Duration: 4h 56m

Affected: Web applicationDetectionCTI Search

Timeline · 3 updates

identified Mar 06, 2026, 10:56 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.
monitoring Mar 06, 2026, 11:00 AM UTC

A fix has been implemented and we are monitoring the results.
resolved Mar 06, 2026, 03:53 PM UTC

This incident has been resolved.

Read the full incident report →

Critical October 6, 2025

Platform outage

Detected by Pingoru: Oct 06, 2025, 04:21 PM UTC
Resolved: Oct 06, 2025, 06:51 PM UTC
Duration: 2h 30m

Affected: Web applicationEvent ingestionEvent storageDetectionHuntingCase managementAutomationAICTI SearchCTI Feed (API)CTI Feed (TAXII)

Timeline · 4 updates

investigating Oct 06, 2025, 04:21 PM UTC

We are investigating an infrastructure incident impacting access to Sekoia.io platform. Initial indications point to an upstream provider incident; investigation with the provider is ongoing.
identified Oct 06, 2025, 05:54 PM UTC

An upstream cloud provider network outage affecting as caused loss of access to the platform.
monitoring Oct 06, 2025, 05:58 PM UTC

The cloud provider reported a global network outage and indicates restoration. Our initial checks show full recovery of the region, but some additional verification are still in progress. We appreciate your patience and will provide updates as soon as we have more information.
resolved Oct 06, 2025, 06:51 PM UTC

All components have been tested and are operational. This incident is now resolved. We appreciate your patience and apologize for any inconvenience caused by this incident.

Read the full incident report →

Minor August 21, 2025

Network incident after routine reboots

Detected by Pingoru: Aug 21, 2025, 10:29 AM UTC
Resolved: Aug 21, 2025, 04:34 PM UTC
Duration: 6h 5m

Affected: Web application

Timeline · 3 updates

identified Aug 21, 2025, 10:29 AM UTC

We have identified an issue with one of our nodes in the MCO1 region during a routine reboot operation. The node failed to recover, causing some connectivity issues within the region. The error was due to an installed version of iptables on the affected node, which interfered with our system's internal mechanisms. After performing some fixes, connectivity is now being restored. We are monitoring the situation closely to ensure full recovery. Please note that event ingestion and processing has not been impacted by this incident, only frontend and API access. Thank you for your patience.
monitoring Aug 21, 2025, 10:56 AM UTC

We have resolved the connectivity issue in the MCO1 region. The root cause was identified as a discrepancy in the nftables rules definitions between different nodes. We have corrected the rules on the affected node and have taken measures to prevent further similar issues. The region is now fully operational. We continue to monitor the situation and we are applying the necessary fixes to other nodes as a preventative measure. We appreciate your understanding during this incident.
resolved Aug 21, 2025, 04:34 PM UTC

The incident in the MCO1 region has been fully resolved. We've taken corrective measures to prevent a recurrence. All systems are now fully operational and stable. We appreciate your patience and understanding during this incident.

Read the full incident report →

Minor August 5, 2025

MCO1 data indexing delays due to storage cluster performance issues

Detected by Pingoru: Aug 05, 2025, 08:40 AM UTC
Resolved: Aug 05, 2025, 01:23 PM UTC
Duration: 4h 42m

Affected: Event storage

Timeline · 2 updates

identified Aug 05, 2025, 08:40 AM UTC

We are currently experiencing a performance issue on our storage cluster in the MCO1 region. This is causing delays in data indexing. We suspect the problem to be related to disk performance issues from our cloud provider, similarly to the previous week. Our engineering team is actively investigating and working towards a resolution. We apologize for any inconvenience caused and will provide an update as soon as we have more information.
resolved Aug 05, 2025, 01:23 PM UTC

Everything is back to normal and there is no delay anymore since 12:23 CEST. We are currently in discussion with our cloud provider to avoid these incidents in the future. The situation is under control and has been resolved. Thank you for your patience during this incident.

Read the full incident report →

Minor July 18, 2025

Events indexation delay

Detected by Pingoru: Jul 18, 2025, 02:30 PM UTC
Resolved: Jul 18, 2025, 04:23 PM UTC
Duration: 1h 53m

Affected: Event ingestion

Timeline · 4 updates

investigating Jul 18, 2025, 03:08 PM UTC

We are currently experiencing a delay in event indexation on our MCO1 region due to a significant increase in event rate. This may lead to a delay in alert raising and event processing across the entire region.
identified Jul 18, 2025, 03:09 PM UTC

Our team has identified the reason behind increase in events rate and applied a fix to mitigate the impact. We are actively monitoring the situation and will provide updates as necessary.
monitoring Jul 18, 2025, 03:22 PM UTC

Our engineering team has identified the cause of the event indexation delay in the MCO1 region and implemented a fix. The backlog of events is still processing. We will continue to monitor the situation closely and provide updates as necessary.
resolved Jul 18, 2025, 04:23 PM UTC

This incident has been resolved.

Read the full incident report →