Sekoia FRA2 Outage History

Sekoia FRA2 is up right now

Pingoru has recorded 8 incidents for Sekoia FRA2: 8 in the last 12 months and 4 in the last 90 days.

Source: status.fra2.sekoia.io

8incidents recorded
8last 12 months
4last 90 days
6 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Sekoia FRA2 in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 2026119 of 744 (3%)
June 202600 of 720 (0%)
July 2026311 of 744 (2%)
August 202611 of 744 (0%)
September 202612 of 720 (0%)
October 202600 of 591 (0%)

Incidents, newest first

Critical September 20, 2026 Region unaccessible 1h 50m Web application, Event ingestion, Event storage, Detection

Started Sep 20, 2026, 03:51 PM UTC· resolved Sep 20, 2026, 05:42 PM UTC

  1. investigating Sep 20, 2026, 03:51 PM UTC

    Our Engineering team is investigating an issue impacting access to the region. All services are operating with degraded performances.

  2. identified Sep 20, 2026, 04:32 PM UTC

    The issue has been identified and corrective actions are in progress to restore access to the region.

  3. monitoring Sep 20, 2026, 04:50 PM UTC

    Our Engineering team has restored the access to the region. We are monitoring the recovery of all functionalities.

  4. resolved Sep 20, 2026, 05:42 PM UTC

    Our Engineering team has completed remediation operations. All applications are operational.

Read the full incident report →

Minor August 21, 2026 SSO login and connectors issues 59m Web application, Event ingestion

Started Aug 21, 2026, 02:50 PM UTC· resolved Aug 21, 2026, 03:49 PM UTC

  1. investigating Aug 21, 2026, 02:50 PM UTC

    We're witnessing inability to log in to the platform via SSO and some integrations intakes are experiencing connection issues. The symptoms are ConnectionError, 503 or HTTPSConnectionPool errors. Our engineering team is actively investigating the issue.

  2. identified Aug 21, 2026, 03:01 PM UTC

    The issue has been identified.

  3. monitoring Aug 21, 2026, 03:08 PM UTC

    A fix has been implemented. SSO login is now working as expected. There might be some delay with events being ingested. Our engineering team is monitoring the situation.

  4. resolved Aug 21, 2026, 03:49 PM UTC

    The incident is resolved. SSO and connectors are now working as expected.

Read the full incident report →

Minor July 29, 2026 Ingestion performance degraded 1h 16m Event ingestion, Detection, Queries

Started Jul 29, 2026, 02:10 PM UTC· resolved Jul 29, 2026, 03:26 PM UTC

  1. monitoring Jul 29, 2026, 02:59 PM UTC

    We are currently experiencing lag on our FRA2 event ingestion workflow due to the underlying storage layer issue. The issue is fixed, the platform is now catching up slowly on the backlog of events to process. We appreciate your patience and understanding while we work towards resolving this issue.

  2. resolved Jul 29, 2026, 03:26 PM UTC

    The platform has fully consumed the backlog. This incident has been resolved.

Read the full incident report →

Major July 27, 2026 Storage infrastructure issues 2h 19m Event ingestion, Event storage, Detection

Started Jul 27, 2026, 06:43 PM UTC· resolved Jul 27, 2026, 09:03 PM UTC

  1. identified Jul 27, 2026, 06:43 PM UTC

    We are currently facing an issue affecting our storage infrastructure. Our on-duty team is working to restore full operations as quickly as possible. We thank you for your patience during the resolution of this incident.

  2. identified Jul 27, 2026, 08:31 PM UTC

    Remedial actions have been taken to restore our services, and event ingestion appears to be operational again. We are currently monitoring the system closely to ensure complete stability. Another update will be provided once full recovery is confirmed.

  3. identified Jul 27, 2026, 09:02 PM UTC

    The issues experienced so far appear to be resolved. Core services have stabilized, and systems are currently operating normally. We are continuing to monitor performance closely to ensure sustained stability.

  4. resolved Jul 27, 2026, 09:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 27, 2026 Platform performance degradation 7h 34m Web application, Event ingestion, Event storage, Detection and 3 more

Started Jul 27, 2026, 08:09 AM UTC· resolved Jul 27, 2026, 03:44 PM UTC

  1. investigating Jul 27, 2026, 08:09 AM UTC

    Since approximately 09:00 UTC today, we are experiencing a performance degradation in our storage and processing infrastructure on FRA2. This is causing a growing delay in our data processing pipeline, which may affect how quickly data is indexed and available in the platform for affected customers.

  2. investigating Jul 27, 2026, 08:59 AM UTC

    Our engineering team is remediating the issue in multiple steps. Compute capacity on the affected storage infrastructure was previously increased and that change is now complete We will post an update within 30 minutes or sooner if the situation changes. Thank you for your understanding

  3. investigating Jul 27, 2026, 09:40 AM UTC

    While a reboot was attempted, it did not fully restore system health. We are currently diagnosing anomalies to ensure a safe recovery. Rest assured that our team is working to resolve this. As a precaution, we encourage you to enable client-side buffering mechanisms wherever possible. Thanks for your understanding

  4. identified Jul 27, 2026, 11:08 AM UTC

    Update - While our team is progressively restarting services ensure a safe recovery, performances are still impacted. Rest assured that our team is working to resolve this. As a precaution, we encourage you to enable client-side buffering mechanisms wherever possible. Thanks for your understanding

  5. monitoring Jul 27, 2026, 11:28 AM UTC

    Service has been restored. Our pipeline is currently processing the backlog, which is causing a temporary delay in event processing and alert creation. We expect this lag to clear over the next day. Our team is actively working to reduce this delay as much as possible. Thanks for your understanding

  6. monitoring Jul 27, 2026, 02:56 PM UTC

    Engineering has deployed additional capacity and fast recovery of the backlog is in progress; full normalization is expected shortly.

  7. resolved Jul 27, 2026, 03:44 PM UTC

    The incident in the region has been resolved. Core services have been restored, backlog processing has completed and event ingestion, alerting, and indexation are operating normally. Monitoring remains active for any residual delays. Thank you for your patience and understanding while we worked to resolve this incident.

Read the full incident report →

Major May 21, 2026 Gateway Incident 18h 52m Web application, Event ingestion, Event storage, Detection and 7 more

Started May 21, 2026, 12:39 PM UTC· resolved May 22, 2026, 07:32 AM UTC

  1. investigating May 21, 2026, 12:39 PM UTC

    We are currently experiencing a service disruption in the FRA2 region. Key network communication machines are not reachable, resulting in partial loss of network connectivity with the cluster. Our team is in contact with the cloud infrastructure provider to resolve the issue. We will provide updates as the situation evolves

  2. investigating May 21, 2026, 12:46 PM UTC

    We were able to restart the servers with the help of the our provider. We will monitor the situation and fix the remaining issues.

  3. investigating May 21, 2026, 12:53 PM UTC

    We are continuing to investigate this issue.

  4. resolved May 22, 2026, 07:32 AM UTC

    Servers were restarted around 14:40 CEST Access to the region was possible at 14:45 and the ingestion process started again. All services resumed normal activity at 14:50 Delay on events processing and alert raising was fully consumed at 16:30, and indexation was back to real-time around 21:00 CEST, marking the end of the incident. Thank you for your patience and sorry for the inconvenience.

Read the full incident report →

Minor March 6, 2026 shared event storage cluster maintenance impacts observables and alerts 4h 57m Web application, Detection, CTI Search

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

  1. identified Mar 06, 2026, 10:55 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 →

Major February 17, 2026 Event storage delay 12h 36m Event storage

Started Feb 17, 2026, 11:05 AM UTC· resolved Feb 17, 2026, 11:42 PM UTC

  1. identified Feb 17, 2026, 11:05 AM UTC

    Since this morning, the region has been experiencing degradation due to a significant increase in event traffic. Efforts are ongoing to mitigate the impact. Some intermittent unavailability errors are expected. Scaling of processing components and retention adjustments have been performed to catch up with the event backlog. The situation is being actively monitored and addressed.

  2. monitoring Feb 17, 2026, 12:49 PM UTC

    We've identified the root cause and applied a fix. The platform is now available. We're handling the event backlog, and we'll be back to real-time soon. Thanks for your patience and sorry for the inconvenience

  3. resolved Feb 17, 2026, 11:42 PM UTC

    The storage cluster has fully consumed the backlog. This incident has been resolved.

Read the full incident report →