Resolved after 10 hours 8 minutes, affecting Event ingestion, on May 6, 2026.
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.
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.
Your product runs on more than Sekoia FRA1
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services