Is Sekoia FRA1 down?
Last checked 2m agoNo incidents right now.
Sekoia FRA1 is operational right now. Last checked 2m ago; the most recent incident resolved 3d 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 16 incidents in the last 90 days (96.53% 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- Automation
Timeline · 9 updates
- investigating · Jul 27, 2026, 07:50 AM UTC
An unexpected cloud provider maintenance is currently affecting our Playbooks automations services. Our engineering team is currently investigating the issue and trying to restore services in a timely manner. We thank you for your patience during resolution.
- investigating · Jul 27, 2026, 09:22 AM UTC
We are experiencing an outage caused by an unexpected infrastructure restart. We are pushing our Cloud Provider for immediate resolution to bypass the provider's standard recovery timeframe. We will keep you informed
- identified · Jul 27, 2026, 10:39 AM UTC
We are still pending the restart completion for impacted component infrastructure which is currently impacting our Playbooks functionality. Our engineering team is in permanent contact with cloud provider teams to ensure the restart is performed in a timely manner. We thank you for your patience during resolution.
- identified · Jul 27, 2026, 02:36 PM UTC
We are continuing to work on a fix for this issue.
- identified · Jul 27, 2026, 02:39 PM UTC
Despite cloud provider rollover, the affected resources are still unavailable, and the Playbooks functionality are still heavily impacted. Our engineering teams are still in direct contact with Cloud provider to recover the situation as soon as possible. We thank you for your patience during the resolution of this incident.
- identified · Jul 27, 2026, 06:13 PM UTC
Following an underlying cloud provider issue, we are required to rebuild part of our Playbook infrastructure. Our engineering team is fully focused on re-deploying the environment as quickly and safely as possible.
- monitoring · Jul 28, 2026, 06:13 AM UTC
Our Engineering team has been fully mobilized overnight to rebuild our Playbook infrastructure. Playbooks are now fully available. Our team is now focused on replaying actions and triggers impacted by the incident. We thank you again for your demonstrated patience during the resolution of this incident
- monitoring · Jul 28, 2026, 10:36 AM UTC
Actions and triggers impacted by the incident are being replayed. Our engineering team is monitoring closely the situation, and current estimation provides a completion ETA by 1.30 pm CET for the replay to complete. During the incident, some users faced issues with triggers unable to start and remaining in inconsistent state. Those triggers have been stopped, and can now be restarted manually by users. A final update will be provided when replay operations are complete.
- resolved · Jul 28, 2026, 05:09 PM UTC
The incident has been resolved, we are back to real-time processing, and everything is stable.
Latest: The incident has been resolved, we are back to real-time processing, and everything is stable.
-
- Event ingestionDetection
Timeline · 2 updates
- identified · Jul 13, 2026, 08:00 PM UTC
Our platform is experiencing delays with indexation and detection. The engineering team is fully mobilized to restore real-time indexation and detection in shortest timeframe. We thank you for your patience during resolution.
- resolved · Jul 14, 2026, 12:22 AM UTC
We are back to real-time processing, and everything is stable. Thank you for your patience throughout this incident.
Latest: We are back to real-time processing, and everything is stable. Thank you for your patience throughout this incident.
-
- Web applicationEvent ingestionEvent storageDetectionHuntingCase managementAutomationAI
Timeline · 4 updates
- investigating · Jul 12, 2026, 08:29 AM UTC
We are currently experiencing an incident impacting a large part of our services. It causes lag in event processing/alert-raising/indexing, and API errors on multiple services. Our teams are investigating with our cloud-provider to find the root cause and a solution. Thank you for your patience.
- identified · Jul 12, 2026, 10:12 AM UTC
We identified network component culprit and proceeding to restore services. Thank you for your patience.
- monitoring · Jul 12, 2026, 10:19 AM UTC
All services are back to normal There is still a little delay on the ingestion chain but it's resolving fast and will be caught up in a matter of minutes Our teams are monitoring the resolution and we will be able to close this incident as soon as everything is back to real-time processing Thank you for your patience
- resolved · Jul 12, 2026, 12:12 PM UTC
We are back to real-time processing and everything is stable. Thank you for your patience throughout this incident.
Latest: We are back to real-time processing and everything is stable. Thank you for your patience throughout this incident.
-
- Event storage
Timeline · 4 updates
- investigating · Jun 26, 2026, 08:45 AM UTC
We are experiencing issue on event search, impacting some customers. We are investigating the root cause. Thank you for your patience.
- identified · Jun 26, 2026, 08:55 AM UTC
We identified the issue, the event search is operational, you may experience some lag on search Job. Thank you for your patience.
- monitoring · Jun 26, 2026, 08:58 AM UTC
We are now monitoring the situation
- resolved · Jun 26, 2026, 09:05 AM UTC
All systems are now operational Thank you for your patience.
Latest: All systems are now operational Thank you for your patience.
-
- 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.
-
See the full Sekoia FRA1 outage history
10 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
- Playbooks unable to run ResolvedStarted Jul 27, 2026, 07:50 AM UTC · Resolved Jul 28, 2026, 05:09 PM UTC · 1d 9h
- Started Jul 13, 2026, 08:00 PM UTC · Resolved Jul 14, 2026, 12:22 AM UTC · 4h 21m
- Network incident ResolvedStarted Jul 12, 2026, 08:29 AM UTC · Resolved Jul 12, 2026, 12:12 PM UTC · 3h 42m
- Event search down ResolvedStarted Jun 26, 2026, 08:45 AM UTC · Resolved Jun 26, 2026, 09:05 AM UTC · 20m
- 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