Own Data Outage History

Own Data is up right now

Own Data had 22 outages in the last 2 years totaling 110h 0m of downtime — averaging 0.9 incidents per month.

There were 22 Own Data outages since June 17, 2025 totaling 110h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.owndata.com

Minor May 29, 2026

[Hipaa4] [Archive] Upstream Azure Outage Causing Service Degradation

Detected by Pingoru
May 29, 2026, 05:04 AM UTC
Resolved
Jun 02, 2026, 07:04 PM UTC
Duration
4d 14h
Affected: HIPAA4 (Archive)
Timeline · 6 updates
  1. investigating May 29, 2026, 05:04 AM UTC

    We are currently investigating this incident.

  2. 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.

  3. 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.

  4. 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

  5. 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.

  6. 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.

Read the full incident report →