Sekoia FRA1 experienced a minor incident on May 6, 2026 affecting Event ingestion, lasting 10h 8m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 06, 2026, 10:19 AM UTC
We are experiencing configuration issues affecting multiple communities which are causing delays in event data indexing. Our teams are actively working to resolve the problem and restore normal indexing speed. Updates will be provided as the situation evolves.
- identified May 06, 2026, 02:11 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring May 06, 2026, 02:30 PM UTC
Approximately 32 servers became unresponsive due to high memory usage caused by a malfunction in the ingestion workflow components. A bulk hard reboot of affected servers has been initiated. Customers may experience delays and the ingestion of some events twice during this incident. There is no impact on automation features or playbooks. The situation is now stable and the backlog of events is being processed.
- resolved May 06, 2026, 08:27 PM UTC
This incident has been resolved.
Looking to track Sekoia FRA1 downtime and outages?
Pingoru polls Sekoia FRA1's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Sekoia FRA1 reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Sekoia FRA1 alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required