Sekoia FRA1 incident

FRA1 Event processing stopped

Minor Resolved View vendor source →

Sekoia FRA1 experienced a minor incident on May 16, 2026 affecting Event storage and Detection, lasting 3h 57m. The incident has been resolved; the full update timeline is below.

Started
May 16, 2026, 07:52 AM UTC
Resolved
May 16, 2026, 11:49 AM UTC
Duration
3h 57m
Detected by Pingoru
May 16, 2026, 07:52 AM UTC

Affected components

Event storageDetection

Update timeline

  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.