Own incident
[Hipaa4] [Archive] Upstream Azure Outage Causing Service Degradation
Own experienced a minor incident on May 29, 2026 affecting HIPAA4 (Archive), lasting 4d 14h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 29, 2026, 05:04 AM UTC
We are currently investigating this incident.
- identified May 29, 2026, 05:58 PM UTC
We are investigating reports of degraded service. Upstream provider (Microsoft Azure) is reporting an active incident, and we are assessing impact on our services. Next update in 30 minutes.
- identified May 29, 2026, 06:00 PM UTC
Root cause identified: an active Microsoft Azure incident is impacting upstream dependencies for our services. We are assessing scope and affected components.
- monitoring May 29, 2026, 10:22 PM UTC
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
- identified May 29, 2026, 10:24 PM UTC
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
- monitoring May 30, 2026, 09:35 PM UTC
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.
- resolved Jun 02, 2026, 07:04 PM UTC
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.