Sekoia USA1 Outage History
Sekoia USA1 is up right nowPingoru has recorded 19 incidents for Sekoia USA1: 19 in the last 12 months and 4 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 15 of 720 (2%) |
| May 2026 | 5 | 49 of 744 (7%) |
| June 2026 | 3 | 21 of 720 (3%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 4 | 28 of 744 (4%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 582 (0%) |
Incidents, newest first
Major August 20, 2026 Indexation is not working properly 8h 45m Event ingestion, Event storage
Started Aug 20, 2026, 01:43 PM UTC· resolved Aug 20, 2026, 10:29 PM UTC
- investigating Aug 20, 2026, 01:43 PM UTC
We are currently experiencing degraded performance with event indexing since 14:55 (France Timezone). Our engineering team is actively investigating the issue. We will post updates as soon as more information is available.
- monitoring Aug 20, 2026, 01:53 PM UTC
A fix has been implemented and event indexing is gradually recovering. Our engineering team is closely monitoring the situation while investigating the root cause.
- monitoring Aug 20, 2026, 02:28 PM UTC
Event indexing remains impacted and the backlog is slowly clearing. Our engineering team continues to investigate while working to fully restore nominal performance.
- monitoring Aug 20, 2026, 03:15 PM UTC
We are continuing to experience performance latency as our team carries out required maintenance procedures on several targeted servers. These ongoing operations are necessary to stabilize the environment and return to normal performance. We regret any disruption this may cause and thank you for your patience while we work toward a full resolution.
- monitoring Aug 20, 2026, 04:50 PM UTC
Our Engineering team has stabilized the environement and event ingestion is fully recovered. We will continue to monitor the situation before closing this incident. We thank you for your demonstrated patience during this incident resolution, and apologize for the inconvenience caused.
- monitoring Aug 20, 2026, 07:16 PM UTC
Our Engineering team has stabilized the environement and event ingestion is fully recovered. We still have delays on event storage and we continue to monitor the situation before closing this incident. We thank you for your demonstrated patience during this incident resolution, and apologize for the inconvenience caused.
- resolved Aug 20, 2026, 10:29 PM UTC
This incident has been resolved.
Minor August 14, 2026 Service Disruption – Intelligence Feature 24m CTI Search
Started Aug 14, 2026, 08:12 AM UTC· resolved Aug 14, 2026, 08:37 AM UTC
- investigating Aug 14, 2026, 08:12 AM UTC
We are currently experiencing an issue affecting the Intelligence feature, which is temporarily unavailable. Our engineering team is actively investigating the issue. We will provide updates as soon as more information becomes available.
- monitoring Aug 14, 2026, 08:25 AM UTC
Access to the Intelligence feature has been fully restored. The temporary outage was due to a missing configuration, which was promptly identified and rectified by our engineering team. We apologize for any inconvenience caused.
- resolved Aug 14, 2026, 08:37 AM UTC
This incident has been resolved.
Minor August 4, 2026 2026-08-04 / USA1 // Indexation lag 5h 57m Event ingestion
Started Aug 04, 2026, 04:26 PM UTC· resolved Aug 04, 2026, 10:24 PM UTC
- identified Aug 04, 2026, 04:26 PM UTC
We are aware that event indexation in the USA1 region is currently experiencing a significant delay. Users may notice that recently ingested events are not yet available for search, detection, or investigation — the delay is currently over 50 minutes. All events are being safely retained and will be fully available once indexation is restored. No data loss is occurring. Our engineering team is actively investigating the root cause. We will post an update within 30 minutes or sooner if the situation changes.
- identified Aug 04, 2026, 04:28 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Aug 04, 2026, 05:59 PM UTC
Indexation lag is recovering. Recent events may be delayed for search, detection, and investigation; no data loss reported. Additional processing capacity has been deployed and indexation is progressively catching up; estimated time to fully catch up is approximately one hour.
- resolved Aug 04, 2026, 10:24 PM UTC
Indexation lag is fully processed since 18:45 UTC Thank you for your patience
Minor August 1, 2026 Multiple services impacted by a cloud provider issue 12h 20m Web application, Event storage, Detection, Automation
Started Aug 01, 2026, 09:29 PM UTC· resolved Aug 02, 2026, 09:50 AM UTC
- identified Aug 01, 2026, 09:29 PM UTC
We are facing an issue with our storage cluster causing the ingestion to take lag. The cause has been identified as a node failure on our cloud provider side. They have informed us the issue with the node is currently being handled. We will keep you informed, thank you for your patience
- identified Aug 01, 2026, 10:05 PM UTC
The issue is currently impacting several other services due to an impact on our distributed storage. Automation features (playbooks) and intelligence center are unavailable, and alerts raises are delayed. Our cloud provider is currently working on restoring our service. We are sorry for the inconvenience.
- identified Aug 01, 2026, 11:02 PM UTC
Services are coming back and the situation is resolving. Indexing performances are still degraded, and several playbooks are in error. Our teams are currently working towards a fix. Missed playbook runs will be re-run once the situation is stable. Thank you for your understanding
- resolved Aug 02, 2026, 09:50 AM UTC
This incident has been resolved since 00:00 UTC
Minor June 25, 2026 Event indexation lag 13h 58m Event ingestion
Started Jun 25, 2026, 05:40 PM UTC· resolved Jun 26, 2026, 07:39 AM UTC
- monitoring Jun 25, 2026, 05:40 PM UTC
We're currently experiencing indexation lag. We identified the culprit to improve situation. We are now monitoring until full recovery. Thank you for your patience
- resolved Jun 26, 2026, 07:39 AM UTC
All the indexation lag has been processed since 20:15 UTC. Thank you for your patience
Minor June 17, 2026 Event storage delay 3h 23m Event storage
Started Jun 17, 2026, 08:17 PM UTC· resolved Jun 17, 2026, 11:41 PM UTC
- investigating Jun 17, 2026, 08:17 PM UTC
We are currently suffering from a delay on event storage. Event ingestion is not impacted. Our team are already working on resolving this incident. We apologize for the inconvenience.
- identified Jun 17, 2026, 08:19 PM UTC
We are currently suffering from a delay on event storage. Event ingestion is not impacted and no data is lost. Our engineering team is has identified the issue and is preparing a fix. We apologize for the inconvenience.
- monitoring Jun 17, 2026, 08:20 PM UTC
We are currently suffering from a delay on event storage. Event ingestion is not impacted and no data is lost. The situation is currently recovering and there is still some delay. The team is currently monitoring the event storage cluster. We apologize for the inconvenience.
- resolved Jun 17, 2026, 11:41 PM UTC
The incident on the event storage cluste is resolved. Event ingestion was not impacted, alert detection was not impacted and no data is lost. The region is fully operational.
Minor June 2, 2026 Indexing performance issues 3h 13m Event storage
Started Jun 02, 2026, 07:20 PM UTC· resolved Jun 02, 2026, 10:33 PM UTC
- identified Jun 02, 2026, 07:20 PM UTC
An issue on our storage cluster has resulted in lower indexing performance that usual, causing indexing delay. Rest assured event processing, detection and alert raising are still done in real-time. Our engineering team is actively working on the issue to restore full performances. Thank you for your understanding.
- monitoring Jun 02, 2026, 08:04 PM UTC
Performances are back to normal and accumulated events are being indexed. We will come back to you once we are back to real-time indexing. Thank you for your patience.
- resolved Jun 02, 2026, 10:33 PM UTC
We're back to real-time indexing. This incident is now over.
Minor May 21, 2026 Indexation lag 5h 12m Event storage
Started May 21, 2026, 04:03 PM UTC· resolved May 21, 2026, 09:16 PM UTC
- investigating May 21, 2026, 04:03 PM UTC
We're experiencing delays in event indexing, which may impact data processing speed. We're actively working on the situation. Thanks for your patience.
- identified May 21, 2026, 04:20 PM UTC
The issue has been identified. A fix has been deployed and we're actively monitoring the situation
- monitoring May 21, 2026, 05:38 PM UTC
The situation is stabilizing, we're slowly recovering initial performances. We keep monitoring the situation. Thanks for your patience
- resolved May 21, 2026, 09:16 PM UTC
Event indexing performances have been fully recovered, and the system is back to normal. Thank you for your patience.
Minor May 4, 2026 Event storage performance degradation 13h 57m Event ingestion
Started May 04, 2026, 05:38 PM UTC· resolved May 05, 2026, 07:35 AM UTC
- monitoring May 04, 2026, 05:38 PM UTC
We experienced degraded performance in event storage indexation in the region, due to an unexpected load increase. Fixes have been applied and the overall performance is stable now. We are currently catching up on the processing lag. We will keep you updated once indexation is back to real-time. Thank you for you patience.
- monitoring May 04, 2026, 07:46 PM UTC
An unexpected load increase occurred again, this slows down catching up the lag. We are actively working on improving event storage performance. We will keep you updated once indexation is back to real-time. Thank you for you patience.
- monitoring May 04, 2026, 09:25 PM UTC
We are currently catching up on the processing lag. We will keep you updated once indexation is back to real-time. Thank you for you patience.
- monitoring May 04, 2026, 10:26 PM UTC
we are back on real time since few minutes. we continue to monitor any issue. Thank you for you patience.
- resolved May 05, 2026, 07:35 AM UTC
This incident has been resolved.
Minor April 27, 2026 Indexation performance issues 15h 9m Event storage
Started Apr 27, 2026, 03:58 PM UTC· resolved Apr 28, 2026, 07:08 AM UTC
- identified Apr 27, 2026, 03:58 PM UTC
We are currently experiencing performances issues on our storage engine, which causes delay between the processing of events and the events showing on events pages. Detection and alert raising are not impacted and are still done in time. Our teams are currently implementing a fix to restore indexation performances. Thank you for your understanding.
- monitoring Apr 27, 2026, 06:11 PM UTC
A fix has been implemented and performances are back, delay is decreasing. We will keep you updated once indexation is back to real-time. Thank you for you patience.
- resolved Apr 28, 2026, 07:08 AM UTC
Indexation is back to real-time since 23:30 CEST. This incident is over.
Minor March 18, 2026 Event processing delays 14h 10m Event ingestion
Started Mar 18, 2026, 07:54 PM UTC· resolved Mar 19, 2026, 10:04 AM UTC
- monitoring Mar 18, 2026, 07:54 PM UTC
A maintenance operation induced some delay in the processing of events. The situation has been resolved and we are now monitoring the situation.
- resolved Mar 19, 2026, 10:04 AM UTC
This incident has been resolved.
Minor March 6, 2026 shared event storage cluster maintenance impacts observables and alerts 4h 56m Web application, Detection, CTI Search
Started Mar 06, 2026, 10:57 AM UTC· resolved Mar 06, 2026, 03:53 PM UTC
- identified Mar 06, 2026, 10:57 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:01 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.
Minor March 5, 2026 Playbook runs stuck 12m Automation
Started Mar 05, 2026, 04:25 PM UTC· resolved Mar 05, 2026, 04:38 PM UTC
- investigating Mar 05, 2026, 04:25 PM UTC
We are currently investigating an incident impacting Playbook runs. We will keep you posted while our Engineering teams progress in their investigations. Thank you for your patience.
- resolved Mar 05, 2026, 04:38 PM UTC
Our teams have identified and fixed the issue regarding playbook runs. Situation is now back to normal. We thank you for your patience during the resolution.
Minor February 17, 2026 Degraded search jobs 4h 26m Web application
Started Feb 17, 2026, 11:16 AM UTC· resolved Feb 17, 2026, 03:43 PM UTC
- identified Feb 17, 2026, 11:16 AM UTC
We are currently experiencing increased processing times on search queries in the USA1 region. It is impacting every page where events are searched and displayed. Our teams have identified the root cause and already applied fixes that should help mitigating the issue. They are actively working on a long-term solution. Sorry for the inconvenience an thank you for your patience.
- monitoring Feb 17, 2026, 02:40 PM UTC
Our engineers team have implemented a fix and events search performances are back to their nominal state. We will keep monitoring for a while to ensure everything is stable.
- resolved Feb 17, 2026, 03:43 PM UTC
This incident has been resolved.
Critical February 12, 2026 Sekoia application not reachable 11h 46m Web application
Started Feb 12, 2026, 07:52 PM UTC· resolved Feb 13, 2026, 07:39 AM UTC
- investigating Feb 12, 2026, 07:52 PM UTC
An issue has been identified which prevents users connecting to the Platform. Our engineering team is investigating the root cause. We thank you for your patience during the incident resolution.
- monitoring Feb 12, 2026, 10:49 PM UTC
Our engineering team has restored the access to the application. All functionalities are fully operational. We are now processing a backlog of events generated during the incident window.
- resolved Feb 13, 2026, 07:39 AM UTC
Our engineering team has resolved the incident and the platform is operating normally. All functionalities are fully operational, and the backlog of events generated during the incident window has been processed.
Minor November 6, 2025 Indexing delay 4h 39m Event storage
Started Nov 06, 2025, 01:20 PM UTC· resolved Nov 06, 2025, 06:00 PM UTC
- identified Nov 06, 2025, 01:20 PM UTC
The event indexing process is being delayed due to a performance issue on our storage cluster. This will cause delay before events are displayed on the event page. Rest assured the detection and alert raising are still done in real time. Our team is actively working on this issue. We will come back to you once a fix is implemented. Thank you for you patience.
- monitoring Nov 06, 2025, 04:44 PM UTC
The performance issue has been fixed and the indexation is currently in near-real-time. We are consuming the backlog accumulated during the incident alongside real-time indexing. We apologize for the inconvenience.
- resolved Nov 07, 2025, 08:46 AM UTC
This incident has been resolved.