Event indexation delay

Update timeline

1. identified Apr 24, 2026, 03:59 PM UTC

   Today at 12:38 CEST, we have started to progressively deploy our detection engine. Unfortunately, due to a misconfiguration, some events were not indexed into our storage engine, but all events were processed and related alerts were raised. The proportion of non-indexed events increased gradually. This issue was identified at 16:40 CEST and a fix was deployed around 17:00 CEST. We are now working to fix the situation and ensure that all missed events will be correctly pushed to the storage engine. During the issue, the detection engines continued to work as expected and alerts (including their related events) were correctly raised. All events related to alerts were also correctly indexed into our storage engine.

2. identified Apr 24, 2026, 04:58 PM UTC

   Our team is currently deploying a fix in order to index the missed events into the storage engine. Be aware that the process is expected to cause duplicates of some events that were already pushed. Thanks for your patience.

3. monitoring Apr 24, 2026, 06:16 PM UTC

   The fix has been deployed and missed events are currently being indexed into our storage engine. We will continue to inform you on the progress.

4. resolved Apr 25, 2026, 08:50 AM UTC

   All missed events were correctly pushed to our storage engine during the night. This incident is now over. Thank you for your patience throughout this incident.