Is Sekoia FRA1 down?
Last checked 3m agoNo active incidents. All 11 components operational.
Sekoia FRA1 is operational right now. Last checked 3m ago; the most recent incident resolved 4d ago.
Real-time Sekoia FRA1 status, recent outages, and incident history: pulled directly from Sekoia FRA1's official status page at status.fra1.sekoia.io every 5 minutes. Pingoru tracks 11 Sekoia FRA1 services and has captured 28 incidents in the last 90 days (99.35% uptime). Get email, Slack, Discord, or webhook alerts the moment Sekoia FRA1 reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- Automation
Timeline · 5 updates
- investigating · Oct 29, 2026, 02:05 PM UTC
We are currently experiencing an issue with our playbook execution engine. New playbooks cannot be started at this time. Our team is actively investigating and working on a fix. We will provide an update as soon as we have more information.
- investigating · Oct 29, 2026, 02:37 PM UTC
We are still investigating the root cause of the issue. In parallel, our team is carrying out operations on our infrastructure to resolve the problem. New playbooks still cannot be started at this time. We will share another update as soon as possible.
- identified · Oct 29, 2026, 03:09 PM UTC
Playbook executions have resumed and the backlog is being processed progressively. Our team is working to speed up the processing of pending executions and to put measures in place to prevent this issue from happening again. We will share another update as soon as possible.
- monitoring · Oct 29, 2026, 04:10 PM UTC
We have applied fixes to our infrastructure to absorb the remaining load of pending playbooks, and executions are now running normally. All pending playbooks should now have been processed. Our team continues to monitor the situation closely.
- resolved · Oct 29, 2026, 04:57 PM UTC
The playbook service is fully operational and this incident is now closed. The execution lag has been fully caught up, and all pending playbooks have been processed.
Latest: The playbook service is fully operational and this incident is now closed. The execution lag has been fully caught up, and all pending playbooks have been processed.
-
- Automation
Timeline · 4 updates
- investigating · Oct 26, 2026, 01:45 AM UTC
We are currently investigating an incident impacting our automations playbooks. Playbooks runs are currently not functional due to a database issue on our platform. We will keep you updated
- identified · Oct 26, 2026, 01:50 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring · Oct 26, 2026, 02:00 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Oct 26, 2026, 02:19 AM UTC
Automations are running again and everything is stable. This incident is now over. Thank you for your patience.
Latest: Automations are running again and everything is stable. This incident is now over. Thank you for your patience.
-
- Event ingestionDetection
Timeline · 2 updates
- identified · Oct 24, 2026, 05:46 PM UTC
Our engineering team has identified an issue with our ingestion pipeline. Remediation actions are in progress.
- resolved · Oct 24, 2026, 06:20 PM UTC
Our Engineering team has completed remediation actions. All systems are operating in real time.
Latest: Our Engineering team has completed remediation actions. All systems are operating in real time.
-
- DetectionAI
Timeline · 3 updates
- investigating · Oct 22, 2026, 08:02 AM UTC
We are currently experiencing an issue affecting the service responsible for running SOL detection rules and Elevate. As a result, some detections may be delayed or not triggered as expected. Our team is actively working on resolving this issue as a top priority. We will provide an update as soon as we have more information. We apologize for any inconvenience this may cause.
- monitoring · Oct 22, 2026, 08:09 AM UTC
The service responsible for running SOL detection rules and Elevate is gradually recovering. The backlog of pending events is currently being processed, so some detections may still be delayed for a short period. Our team is closely monitoring the situation until processing is fully back to normal. We will provide a final update once the backlog has been fully cleared. We apologize for any inconvenience this may cause.
- resolved · Oct 22, 2026, 09:01 AM UTC
The issue affecting the service responsible for running SOL detection rules and Elevate has been resolved. The backlog has been fully processed and detections are now running normally, with no remaining impact. We will continue to monitor the service closely. We apologize for any inconvenience this may have caused and thank you for your patience.
Latest: The issue affecting the service responsible for running SOL detection rules and Elevate has been resolved. The backlog has been fully processed and detections are now running norma…
-
- Event ingestionDetection
Timeline · 4 updates
- investigating · Oct 14, 2026, 03:15 PM UTC
We are currently investigating issues in loading events and alerts pages. Our teams are working on identifying the issue. We'll provide an update as soon as we have more to share.
- identified · Oct 14, 2026, 03:37 PM UTC
Our teams have identified the issue and are applying remediation actions. We expect loading to return to normal in the upcoming minutes.
- monitoring · Oct 14, 2026, 03:41 PM UTC
The issue has been resolved, and loading seems to be working as expected. We are continuing to monitor the loading of both alerts and events pages.
- resolved · Oct 14, 2026, 03:55 PM UTC
The service is operational. Thank you for bearing with us while we worked through the investigation and resolution.
Latest: The service is operational. Thank you for bearing with us while we worked through the investigation and resolution.
-
See the full Sekoia FRA1 outage history
23 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
Incident record
Since April 2026 · Statuspage by Atlassian · 11 components checked every 5 minutesThe longest incident in the last year, FRA1 storage cluster is unstable on February 10, 2026, ran for 3 days. 2 maintenance windows announced in the same period.
Most affected components, last 12 months
- Event ingestion29
- Detection24
- Event storage18
- Automation12
- Queries12
Latest incidents
- Playbook execution disruption
We are currently experiencing an issue with our playbook execution engine. New playbooks cannot be started at this time. Our team is actively investigating and…
- Automations issue
We are currently investigating an incident impacting our automations playbooks. Playbooks runs are currently not functional due to a database issue on our…
- Delay in Events processing
Our engineering team has identified an issue with our ingestion pipeline. Remediation actions are in progress.
- Playbook execution disruption ResolvedStarted Oct 29, 2026, 02:05 PM UTC · Resolved Oct 29, 2026, 04:57 PM UTC · 2h 52m
- Automations issue ResolvedStarted Oct 26, 2026, 01:45 AM UTC · Resolved Oct 26, 2026, 02:19 AM UTC · 33m
- Delay in Events processing ResolvedStarted Oct 24, 2026, 05:46 PM UTC · Resolved Oct 24, 2026, 06:20 PM UTC · 33m
- Started Oct 22, 2026, 08:02 AM UTC · Resolved Oct 22, 2026, 09:01 AM UTC · 58m
- Started Oct 14, 2026, 03:15 PM UTC · Resolved Oct 14, 2026, 03:55 PM UTC · 40m
- Web application slowness ResolvedStarted Oct 14, 2026, 03:14 PM UTC · Resolved Oct 14, 2026, 03:23 PM UTC · 9m
- Latency on correlation process ResolvedStarted Oct 08, 2026, 02:41 PM UTC · Resolved Oct 08, 2026, 03:12 PM UTC · 30m
- Some AI analyses may be unavailable ResolvedStarted Oct 07, 2026, 12:44 PM UTC · Resolved Oct 07, 2026, 01:56 PM UTC · 1h 12m