Own Outage History

Own is up right now

Pingoru has recorded 14 incidents for Own: 10 in the last 12 months and 2 in the last 90 days.

Source: status.owndata.com

14incidents recorded

10last 12 months

2last 90 days

13 hourstypical duration

Incidents per month

Share of hours with an open incident, any severity

Pingoru began tracking Own in April 2026, so earlier months are not shown. Hover a bar for its value.

Show as a table

Month	Incidents	Hours with an open incident
April 2026	1	0 of 720 (0%)
May 2026	1	67 of 744 (9%)
June 2026	1	51 of 720 (7%)
July 2026	0	0 of 744 (0%)
August 2026	2	12 of 744 (2%)
September 2026	0	0 of 720 (0%)
October 2026	0	0 of 563 (0%)

Incidents, newest first

Major August 22, 2026 Service disruption in CA4 Azure 6h 6m CA4 (Backup & Recover)

Started Aug 22, 2026, 11:00 AM UTC· resolved Aug 22, 2026, 05:06 PM UTC

identified Aug 22, 2026, 11:00 AM UTC

We experience service disruption for backups and jobs in CA4
resolved Aug 22, 2026, 05:06 PM UTC

This incident has been resolved.

Read the full incident report →

Minor August 4, 2026 Product UI degradation 6h 13m HIPAA4 (Backup & Recover), HIPAA4 (Archive), HIPAA4 (Data Mask & Seed), CA4 (Backup & Recover) and 5 more

Started Aug 04, 2026, 05:30 AM UTC· resolved Aug 04, 2026, 11:43 AM UTC

investigating Aug 04, 2026, 05:30 AM UTC

Customers may currently experience disruptions to the user interface of our products. Backups, scheduled jobs, and API traffic are not impacted and continue to operate normally. We are actively working to restore the UI to full service and will provide updates as the situation progresses.
investigating Aug 04, 2026, 07:38 AM UTC

We are currently investigating this incident.
monitoring Aug 04, 2026, 08:00 AM UTC

We implemented a fix and are currently monitoring the result.
resolved Aug 04, 2026, 11:43 AM UTC

This incident has been resolved.

Read the full incident report →

Notice June 21, 2026 CA4 - Archive Service Outage Impacting Archive services and UI Access 8h 2m CA4 (Archive)

Started Jun 21, 2026, 08:45 AM UTC· resolved Jun 21, 2026, 04:47 PM UTC

investigating Jun 21, 2026, 08:45 AM UTC

We are currently investigating this incident. Customers may experience high latency while using archive on azure ca4
investigating Jun 21, 2026, 11:04 AM UTC

We're currently experiencing an issue affecting the Archive service. Customers may be unable to search archived data and the UI is not available access or manage archive policies, and perform related operations. We are continuing to work on a fix for this incident.
monitoring Jun 21, 2026, 04:25 PM UTC

The incident has been resolved. We are closely monitoring the service to verify its full recovery.
resolved Jun 21, 2026, 04:47 PM UTC

This incident has been resolved.

Read the full incident report →

Minor May 29, 2026 [Hipaa4] [Archive] Upstream Azure Outage Causing Service Degradation 4d 14h HIPAA4 (Archive)

Started May 29, 2026, 05:04 AM UTC· resolved Jun 02, 2026, 07:04 PM UTC

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.