Sekoia FRA1 incident
Alert retrieval delays due to cache failover issue
Resolved after 3 hours 47 minutes, affecting Detection, on December 26, 2025.
Alert processing is fully operational, and all queued alerts have been processed. Our investigation found no alert loss. This incident is resolved, and we apologize for any inconvenience this may have caused.
Affected components
Update timeline
- investigating Dec 26, 2025, 10:55 AM UTC
Starting from 7:30, alert retrievals have been delayed due to a failover issue in the sightings cache cluster causing data read inconsistencies. The primary sightings cache instance was manually stopped to force the failover to the secondary instance. Investigation and recovery efforts are ongoing. Customers may experience delays in alert updates during this time.
- identified Dec 26, 2025, 11:13 AM UTC
Following the manual failover of the sightings cache cluster primary instance, alert retrieval processing has resumed and backlog processing is underway. The fix has restored normal operation and alerts are being consumed again. Monitoring is ongoing to ensure full recovery.
- resolved Dec 26, 2025, 02:42 PM UTC
Alert processing is fully operational, and all queued alerts have been processed. Our investigation found no alert loss. This incident is resolved, and we apologize for any inconvenience this may have caused.
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