Own Data incident
[Hipaa4] [Archive] Upstream Azure Outage Causing Service Degradation
Own Data experienced a major incident on May 29, 2026, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved May 29, 2026, 05:04 AM UTC
Type: Incident Duration: 4 days, 14 hours and 1 minute Affected Components: Archive May 29, 22:24:50 GMT+0 - Identified - Microsoft Azure has confirmed a datacenter power outage as the source. Elastic Cloud (hosted on Azure) is degraded, which is impacting our cluster performance. Customer-facing services are not affected at this time. We are waiting on Elastic Cloud to confirm recovery May 30, 21:35:30 GMT+0 - Monitoring - The search service has been restored to full capacity. Working with Elastic support, we completed the recovery actions and the cluster is healthy. Background rebalancing across the cluster is still in progress. We are monitoring until it completes. Jun 2, 19:04:30 GMT+0 - Resolved - The Archive search service is fully restored. The upstream Microsoft Azure outage has been resolved, our Elastic Cloud cluster is healthy, and rebalancing is complete. No customer action is required. Thank you for your patience. May 29, 05:04:00 GMT+0 - Investigating - We are investigating reports of degraded service. Upstream provider (Microsoft Azure) is reporting an active incident, and we are assessing impact on our services. May 29, 18:00:37 GMT+0 - Identified - Root cause identified: an active Microsoft Azure incident is impacting upstream dependencies for our services. We are assessing scope and affected components.