Sekoia UAE1 Outage History

Sekoia UAE1 is up right now

Sekoia UAE1 had 8 outages in the last 2 years totaling 43h 3m of downtime — averaging 0.3 incidents per month.

There were 8 Sekoia UAE1 outages since March 6, 2026 totaling 43h 3m of downtime. Each is summarised below — incident details, duration, and resolution information.

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

Major July 26, 2026

Massive underlying storage incident

Detected by Pingoru
Jul 26, 2026, 08:30 AM UTC
Resolved
Jul 26, 2026, 09:36 AM UTC
Duration
1h 6m
Affected: Web applicationEvent ingestionEvent storageDetectionQueriesCasesAutomationAICTI SearchCTI Feed (API & TAXII)CTI Feed (TAXII)
Timeline · 6 updates
  1. investigating Jul 26, 2026, 08:30 AM UTC

    We currently having issue on our underlying storage which impact several features. We are investigating.

  2. investigating Jul 26, 2026, 08:31 AM UTC

    We are continuing to investigate this issue.

  3. identified Jul 26, 2026, 09:02 AM UTC

    We identified the problem, Ingestion is back, we are restoring the region.

  4. identified Jul 26, 2026, 09:04 AM UTC

    Our engineering team has identified the root cause: a failure in the underlying storage infrastructure caused by memory pressure on storage components. We have applied a fix: storage component memory allocation has been significantly increased and a recovery deployment is actively rolling out. We are already seeing early signs of improvement, with storage components beginning to come back online. Some processing services have been temporarily suspended to allow the storage layer to recover cleanly and safely. We will post an update within 20 minutes or sooner if the situation changes.

  5. monitoring Jul 26, 2026, 09:25 AM UTC

    We are pleased to confirm that all services in the UAE1 region have been restored and are fully operational. Ingestion, detection, and automated response capabilities are running normally. The backlog of events that accumulated during the disruption has been processed. Our engineering team is actively monitoring the region to ensure continued stability. We will provide a further update once we have confirmed sustained recovery.

  6. resolved Jul 26, 2026, 09:36 AM UTC

    The UAE1 region has been fully restored. All services are running normally. The on-call team is continuing a post-incident investigation.

Read the full incident report →

Major July 25, 2026

Massive underlying storage

Detected by Pingoru
Jul 25, 2026, 02:20 PM UTC
Resolved
Jul 25, 2026, 03:54 PM UTC
Duration
1h 34m
Affected: Web applicationEvent ingestionEvent storageDetectionQueriesCasesAutomation
Timeline · 4 updates
  1. investigating Jul 25, 2026, 02:20 PM UTC

    We currently having issue on our underlying storage which impact several features. We are investigation

  2. identified Jul 25, 2026, 02:29 PM UTC

    We identified the failing component and applying a fix. We'll keep you posted of the progress

  3. monitoring Jul 25, 2026, 02:40 PM UTC

    The situation is recovering. Thank you for your patience

  4. resolved Jul 25, 2026, 03:54 PM UTC

    The platform is now fully operational. All services have been restored, backlog processing completed and there are no active alerts. Thank you for your patience.

Read the full incident report →

Major July 9, 2026

Indexation Lag

Detected by Pingoru
Jul 09, 2026, 08:12 AM UTC
Resolved
Jul 09, 2026, 10:53 PM UTC
Duration
14h 41m
Affected: Web applicationEvent ingestionEvent storageDetectionQueriesCasesAutomationAICTI SearchCTI Feed (API & TAXII)CTI Feed (TAXII)
Timeline · 6 updates
  1. investigating Jul 09, 2026, 08:12 AM UTC

    We currently have issue with our indexation storage cluster. Investigation is in progress to identify and fix the issue. We are sorry for the inconvenience.

  2. investigating Jul 09, 2026, 09:11 AM UTC

    We are continuing to investigate this issue.

  3. identified Jul 09, 2026, 12:07 PM UTC

    Event ingestion remains delayed with a significant backlog and indexing has not fully resumed. Mitigations are in progress. Work continues to restore normal ingestion, updates will follow. Thank you for your patience

  4. identified Jul 09, 2026, 02:58 PM UTC

    A fix has been deployed to restore event ingestion and reduce the backlog; teams are closely monitoring progress and will provide an update when normal indexing is confirmed. Thank you for your patience

  5. monitoring Jul 09, 2026, 04:04 PM UTC

    The deployed fix to restore event ingestion works as expected. We're now closely monitoring the situation. The backlog is being processed. Thank you for your patience

  6. resolved Jul 09, 2026, 10:53 PM UTC

    This incident has been resolved. All backlog events were ingested.

Read the full incident report →

Major June 24, 2026

Alert processing is interrupted

Detected by Pingoru
Jun 24, 2026, 11:07 AM UTC
Resolved
Jun 24, 2026, 11:31 AM UTC
Duration
24m
Affected: Detection
Timeline · 2 updates
  1. identified Jun 24, 2026, 11:07 AM UTC

    We identified an issue on the alert processing. Currently alerts are not being raised in real-time since 12:24 CEST. Our response team is investigating the issue. We apologize for the inconvenience.

  2. resolved Jun 24, 2026, 11:31 AM UTC

    The cause has been identified and fixed. Alerts are being raised in real-time again. No alerts were lost and all associated data should be available. We apologize for the inconvenience.

Read the full incident report →

Major June 18, 2026

Ongoing incident storage incident

Detected by Pingoru
Jun 18, 2026, 08:37 PM UTC
Resolved
Jun 19, 2026, 12:01 AM UTC
Duration
3h 24m
Affected: Event ingestion
Timeline · 3 updates
  1. investigating Jun 18, 2026, 08:37 PM UTC

    Ongoing incident storage for several services. Event storage cluster is affected, causing indexing to be down. Teams are investigating and working on restoration.

  2. monitoring Jun 18, 2026, 10:43 PM UTC

    We identified and fixed the storage issue, event indexing and workflow processing are catching up. Teams continue to monitor recovery.

  3. resolved Jun 19, 2026, 12:01 AM UTC

    The storage cluster issue is fixed, event indexing and event processing are back in real time.

Read the full incident report →

Minor June 11, 2026

Event storage slowness

Detected by Pingoru
Jun 11, 2026, 12:56 PM UTC
Resolved
Jun 11, 2026, 02:49 PM UTC
Duration
1h 53m
Affected: Event storage
Timeline · 4 updates
  1. investigating Jun 11, 2026, 12:56 PM UTC

    An ongoing incident in the UAE1 region is impacting event storage. This is causing delays on event indexing process. Engineering teams are actively investigating.

  2. identified Jun 11, 2026, 12:58 PM UTC

    We identified and mitigated the event storage slowness impact. Thanks for your patience

  3. monitoring Jun 11, 2026, 01:02 PM UTC

    The situation is improving and our engineering teams are actively monitoring the event storage cluster

  4. resolved Jun 11, 2026, 02:49 PM UTC

    The incident is now resolved. Event ingestion lag returned to expected levels and no customer impact is currently observed. Follow-up actions to prevent recurrence are in progress. Thank you for your patience

Read the full incident report →

Minor May 25, 2026

Delay in events processing

Detected by Pingoru
May 25, 2026, 06:02 AM UTC
Resolved
May 25, 2026, 09:05 PM UTC
Duration
15h 2m
Affected: Event ingestion
Timeline · 6 updates
  1. investigating May 25, 2026, 06:02 AM UTC

    Our Engineering team is currently investigating an issue causing some delay on events processing.

  2. monitoring May 25, 2026, 07:48 AM UTC

    Our Engineering team has identified the issue and applied remediation actions. Situation is being monitored until complete recovery. We thank you for your patience during resolution.

  3. identified May 25, 2026, 11:17 AM UTC

    The underlying performance issue is still present and our teams are currently working on scaling to find better performances. Events ingestion, detection and alerts raising are not impacted and still done in real-time. Thank you for your understanding.

  4. monitoring May 25, 2026, 11:46 AM UTC

    Our Engineering continues performing long term stabilization actions. User impact has been resolved. We thank you for your patience during resolution.

  5. monitoring May 25, 2026, 06:54 PM UTC

    The scale has been progressively deployed and the platform has been catching up on the indexing delay since 16:00 CEST. It is expected to catch up in a couple hours. Our engineering team will also implement some long-term fixes during the evening and the night to increase performances. We will let you know once the platform is back to real-time. Thank you for your patience.

  6. resolved May 25, 2026, 09:05 PM UTC

    The platform has processed all the accumulated delay and is back to real-time indexing. Everything is stable, this incident is over. Our team has started working on long-term improvements. Thank you for your patience throughout this incident.

Read the full incident report →

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
  1. 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.

  2. monitoring Mar 06, 2026, 11:00 AM UTC

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

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

    This incident has been resolved.

Read the full incident report →