Massive underlying storage incident

Update timeline

1. investigating Jul 26, 2026, 08:30 AM UTC

   We currently having issue on our underlying storage which impact several features. We are investigating.

2. investigating Jul 26, 2026, 08:31 AM UTC

   We are continuing to investigate this issue.

3. identified Jul 26, 2026, 09:02 AM UTC

   We identified the problem, Ingestion is back, we are restoring the region.

4. identified Jul 26, 2026, 09:04 AM UTC

   Our engineering team has identified the root cause: a failure in the underlying storage infrastructure caused by memory pressure on storage components. We have applied a fix: storage component memory allocation has been significantly increased and a recovery deployment is actively rolling out. We are already seeing early signs of improvement, with storage components beginning to come back online. Some processing services have been temporarily suspended to allow the storage layer to recover cleanly and safely. We will post an update within 20 minutes or sooner if the situation changes.

5. monitoring Jul 26, 2026, 09:25 AM UTC

   We are pleased to confirm that all services in the UAE1 region have been restored and are fully operational. Ingestion, detection, and automated response capabilities are running normally. The backlog of events that accumulated during the disruption has been processed. Our engineering team is actively monitoring the region to ensure continued stability. We will provide a further update once we have confirmed sustained recovery.

6. resolved Jul 26, 2026, 09:36 AM UTC

   The UAE1 region has been fully restored. All services are running normally. The on-call team is continuing a post-incident investigation.