Is Sekoia FRA1 down?
Last checked 1m agoNo incidents right now.
Sekoia FRA1 is operational right now. Last checked 1m ago; the most recent incident resolved 9d ago.
Real-time Sekoia FRA1 status, recent outages, and incident history — pulled directly from Sekoia FRA1's official status page at https://status.fra1.sekoia.io every 5 minutes. Pingoru tracks 12 Sekoia FRA1 services and has captured 19 incidents in the last 90 days (96.71% uptime). Get email, Slack, Discord, or webhook alerts the moment Sekoia FRA1 reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Event storageHunting
Timeline · 4 updates
- investigating · Jun 03, 2026, 03:10 PM UTC
An ongoing incident is currently impacting event indexing and searches for some customers. Engineers are investigating on the issue.
- identified · Jun 03, 2026, 03:11 PM UTC
An ongoing incident in the FRA1 region is impacting event indexing and search capabilities for some customers. The event storage is experiencing some failures which causes unstabilities, this results in delayed ingestion and unavailable searches. Engineers are investigating and working on mitigations to restore indexing and search functionality.
- monitoring · Jun 03, 2026, 05:41 PM UTC
The underlying infrastructure have been stabilized and indexing has resumed, we're currently catching event indexing lag.
- resolved · Jun 04, 2026, 08:58 AM UTC
This incident has been resolved. All events are being indexed in real time and available for searches.
Latest: This incident has been resolved. All events are being indexed in real time and available for searches.
-
- Detection
Timeline · 3 updates
- identified · Jun 01, 2026, 10:24 AM UTC
An ongoing incident is impacting detection services due to a failure in cache instances. Engineers are performing restarts and recovery steps; service restoration is in progress but may take some time.
- monitoring · Jun 01, 2026, 10:32 AM UTC
Detection workflows were unavailable due to a cluster of cache instances becoming unresponsive after a deployment. The workflows have been restarted and all services are back online; event processing may be delayed but recovery and catch-up are in progress.
- resolved · Jun 01, 2026, 05:11 PM UTC
Backlog has been processed since 18:40 CEST and systems are stable. Thank you for your patience
Latest: Backlog has been processed since 18:40 CEST and systems are stable. Thank you for your patience
-
- Event storage
Timeline · 4 updates
- investigating · May 29, 2026, 05:57 PM UTC
We are currently facing an issue on our event storage impacting only some customers, impacting indexation and researches. Our engineering team is actively working on diagnosing the root cause and finding a solution. Thank you for you patience.
- identified · May 29, 2026, 07:12 PM UTC
The root cause has been identified, and our team is currently applying patches. Event indexing was delayed for the impacted communities, which means some events may appear late on event pages. Indexing is now running and processing the backlog. Search is available again. We will keep you updated.
- monitoring · May 29, 2026, 07:50 PM UTC
The patches have been applied by our engineering team, and the situation is stable again. Accumulated logs are being processed. We will keep you updated once indexing is back to real time. Thank you for your patience.
- resolved · May 29, 2026, 11:09 PM UTC
Indexing is in real-time for all communities since 23:15 CEST. Everything is stable. Thank you for your patience throughout this incident.
Latest: Indexing is in real-time for all communities since 23:15 CEST. Everything is stable. Thank you for your patience throughout this incident.
-
- Automation
Timeline · 4 updates
- investigating · May 28, 2026, 07:36 AM UTC
An ongoing incident is affecting automation features: playbook actions are not being triggered. Customers may experience failures of automated workflows. Engineering teams are investigating and working on a fix.
- identified · May 28, 2026, 09:24 AM UTC
Engineers identified and isolated the offending playbook and restored real-time processing. A backlog playbook tasks remains and customers may see delayed automated workflows while the backlog is processed. Teams continue to work on completing the backlog.
- monitoring · May 28, 2026, 09:37 AM UTC
Teams continue to work on completing the backlog
- resolved · May 28, 2026, 01:03 PM UTC
All the backlog has been processed Thanks for you patience
Latest: All the backlog has been processed Thanks for you patience
-
- Automation
Timeline · 4 updates
- investigating · May 20, 2026, 12:53 PM UTC
We are currently experiencing a major incident affecting the automation features in the FRA1 cloud region. An excessive number of automation playbook runs are being triggered overwhelming the system and causing no new playbook runs to be processed. We are investigating the issue.
- identified · May 20, 2026, 01:23 PM UTC
The major incident affecting automation features in the FRA1 cloud region is currently under recovery. The automation feature for playbooks runs was stopped to mitigate the issue and is now being restarted gradually. Customers may still experience delays in playbook runs, but recovery is in progress.
- monitoring · May 20, 2026, 04:34 PM UTC
The automation feature has been fully restored, with real-time processing resumed. We are currently handling the backlog of tasks which couldn't be handled in time.
- resolved · May 20, 2026, 09:45 PM UTC
The backlog of tasks has been processed and the automation feature is fully restored.
Latest: The backlog of tasks has been processed and the automation feature is fully restored.
-
See the full Sekoia FRA1 outage history
14 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Sekoia FRA1 outage history →Or sign up free to get alerts when Sekoia FRA1 breaks · 10 free monitors · No credit card
- Storage cluster is degraded ResolvedStarted Jun 03, 2026, 03:10 PM UTC · Resolved Jun 04, 2026, 06:15 PM UTC · 1d 3h
- Started Jun 01, 2026, 10:24 AM UTC · Resolved Jun 01, 2026, 05:11 PM UTC · 6h 47m
- Started May 29, 2026, 05:57 PM UTC · Resolved May 29, 2026, 11:09 PM UTC · 5h 12m
- Automation features unavailable ResolvedStarted May 28, 2026, 07:36 AM UTC · Resolved May 28, 2026, 01:03 PM UTC · 5h 27m
- Started May 20, 2026, 12:53 PM UTC · Resolved May 20, 2026, 09:45 PM UTC · 8h 51m
- Partial indexing lag ResolvedStarted May 18, 2026, 07:40 AM UTC · Resolved May 18, 2026, 10:31 AM UTC · 2h 50m
- Storage indexing lag ResolvedStarted May 17, 2026, 07:31 AM UTC · Resolved May 17, 2026, 10:28 AM UTC · 2h 56m
- FRA1 Event processing stopped ResolvedStarted May 16, 2026, 07:52 AM UTC · Resolved May 16, 2026, 11:49 AM UTC · 3h 57m