Is Sekoia FRA1 down?

We are currently investigating an issue that may cause event details to load slowly. In some cases, alerts may also be raised without their related events being attached. Our engineering teams are actively working to identify the root cause and resolve the issue. We will provide further updates as soon as more information becomes available.

Our teams have identified the issue and are working through remediation actions.

All remediation actions have been performed and impacted services are showing positive signs of recovery. Our teams are monitoring the situation.

The situation is stable and the incident is resolved. The remediation actions put in place have restored service stability.

We are currently investigating an issue affecting our event pipeline : alerts are being raised without the related events being attached to them. Our teams are currently investigating. We'll keep you posted as soon as possible.

We have resumed normal operations across both the workflow and search systems. We are currently investigating why we had some issues in the first place

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

The situation remains stable, and the incident is resolved. We identified an issue in the way some services were managing database connections. The mitigations put in place have restored service stability. Our teams will continue working on a permanent fix to prevent the issue from recurring.

Our engineering teams have detected and investigating an issue. Some of our customers might experience delay in events ingestion. An update will be provided as soon as possible to inform about remediation actions. We thank you for your patience during resolution.

The issue affecting our KeyDB infrastructure has recurred and may affect detection services. Our teams are restarting the affected components as a temporary measure to restore service while we continue investigating the root cause. The service should be partially restored soon. We will provide another update as soon as more information is available.

Restarting the affected components has not fully restored service. Detection may be delayed while the issue persists. Our teams are investigating a problem that appears to be related to the underlying cache management component. We are evaluating workarounds and possible solutions.

A fix was implemented and allowed detection and ingestion services to restart. We expect lag to resorb gradually. Our engineering teams are monitoring the situation.

This incident is resolved. Detection process is back in real-time. All events and alert are stored and searchable in real-time. Overall the event ingestion process is in real time. We thank you for your patience during resolution.

Our Engineering team has identified an issue impacting event processing. Users may experience some delays for events to appear in the console. An update will be provided as soon as possible to inform about resolution actions. We thank you for your patience during resolution.

Some services may be unavailable or experience degraded performance because they are unable to establish new connections to a required cache component. Our teams are restarting the affected services to restore normal operation. We will provide an update as soon as more information is available.

Further analysis indicates that this incident may affect our detection services. Our teams are continuing restoration efforts and will provide another update as soon as more information is available.

Service appears to be returning to normal following the restart of an affected backend component. Our initial findings point to an issue affecting our cloud provider’s infrastructure. We are continuing to monitor the service to confirm full stability.

The situation has improved slightly, but ingestion and detection services continue to experience disruptions. The services remain available, although some functionality may be affected. Our teams are continuing to work on restoring normal service.

Following the restart of the affected backend components, some services took longer than expected to reconnect. They have since reconnected automatically, and we are continuing to monitor the service.

The incident has been resolved. Ingestion and Detection services have been recovered.

We are investigating an unexpected increase in load on our authentication endpoints. Our teams are actively investigating the situation.

We have identified the source of the unexpected load and are currently evaluating a proper long-term solution. The additional load is being successfully absorbed, and our teams continue to investigate the situation.

We scaled the database infrastructure bottleneck identified during the investigation and are now able to fully absorb the increased authentication load. The situation is resolved and services are stable. We will continue monitoring closely.

The incident is now resolved. Authentication services are operating normally and the platform is stable. We will continue to monitor the service, but no further impact is expected.