Own Data Outage History

Own Data is up right now

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

Source: status.owndata.com

14incidents recorded
10last 12 months
1last 90 days
19 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Own Data in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202615 of 720 (1%)
May 2026167 of 744 (9%)
June 2026143 of 720 (6%)
July 202600 of 744 (0%)
August 2026212 of 744 (2%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 116 (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

  1. identified Aug 22, 2026, 11:00 AM UTC

    We experience service disruption for backups and jobs in CA4

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

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

  2. investigating Aug 04, 2026, 07:38 AM UTC

    We are currently investigating this incident.

  3. monitoring Aug 04, 2026, 08:00 AM UTC

    We implemented a fix and are currently monitoring the result.

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

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

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

  3. monitoring Jun 21, 2026, 04:25 PM UTC

    The incident has been resolved. We are closely monitoring the service to verify its full recovery.

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

  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 →

Minor April 1, 2026 Degradation in email notification service 5h 4m Overall

Started Apr 01, 2026, 10:00 AM UTC· resolved Apr 01, 2026, 03:04 PM UTC

  1. investigating Apr 01, 2026, 10:00 AM UTC

    We are currently investigating this incident.

  2. identified Apr 01, 2026, 01:39 PM UTC

    We have identified the cause and are working on a resolution. We anticipate a resolution within the next hour.

  3. monitoring Apr 01, 2026, 01:55 PM UTC

    We implemented a fix and are currently monitoring the result.

  4. resolved Apr 01, 2026, 03:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 17, 2026 Salesforce Disruption Impacting Own Recover (Primarily US Regions) 6h 57m Overall

Started Feb 17, 2026, 03:11 AM UTC· resolved Feb 17, 2026, 10:08 AM UTC

  1. monitoring Feb 17, 2026, 03:11 AM UTC

    Own Recover backups are currently affected by a widespread Salesforce service disruption that may result in login failures and intermittent service unavailability. The issue is primarily impacting backup services in US Regions. Technical teams are actively investigating the root cause and implementing remediation measures, with more details available via Salesforce Incident 20003707\.

  2. resolved Feb 17, 2026, 10:08 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 28, 2026 US2 Archive package unavaliable 1h 44m Overall

Started Jan 28, 2026, 09:19 AM UTC· resolved Jan 28, 2026, 11:03 AM UTC

  1. identified Jan 28, 2026, 09:19 AM UTC

    We working on a fix.

  2. resolved Jan 28, 2026, 11:03 AM UTC

    This incident has been resolved.

Read the full incident report →

Major January 18, 2026 [CA1,CA4] Archive console is down 31m Overall

Started Jan 18, 2026, 10:04 AM UTC· resolved Jan 18, 2026, 10:36 AM UTC

  1. investigating Jan 18, 2026, 10:04 AM UTC

    We are currently investigating this incident.

  2. identified Jan 18, 2026, 10:10 AM UTC

    A fix is being implemented.

  3. monitoring Jan 18, 2026, 10:34 AM UTC

    The fix was implemented - CA1 & CA4 are operational.

  4. resolved Jan 18, 2026, 10:36 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 18, 2025 Some backups are experiencing Blockchain Verify degragation 1d 16h Overall

Started Nov 18, 2025, 07:30 PM UTC· resolved Nov 20, 2025, 12:08 PM UTC

  1. identified Nov 18, 2025, 07:30 PM UTC

    Some services' backups are currently failing to be signed with the Blockchain Verify hash signature due to a degradation in the third-party provider's service. Once the provider service degradation is resolved (or recovered), the backups should be successfully signed with the required signatures

  2. resolved Nov 20, 2025, 12:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 17, 2025 Production Services Dashboard Loading Issues in APP1 4h 56m Overall

Started Nov 17, 2025, 04:28 PM UTC· resolved Nov 17, 2025, 09:24 PM UTC

  1. investigating Nov 17, 2025, 04:28 PM UTC

    Some users in APP1 region may experience issues loading their production services dashboard.

  2. identified Nov 17, 2025, 04:41 PM UTC

    We are continuing to work on a hot fix for this incident.

  3. resolved Nov 17, 2025, 09:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 24, 2025 CA1 backups failing 3h 25m Overall

Started Oct 24, 2025, 01:15 AM UTC· resolved Oct 24, 2025, 04:40 AM UTC

  1. investigating Oct 24, 2025, 01:15 AM UTC

    We are currently investigating this incident.

  2. resolved Oct 24, 2025, 04:40 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 22, 2025 US2 service disruption 9h 45m Overall

Started Oct 22, 2025, 02:30 AM UTC· resolved Oct 22, 2025, 12:15 PM UTC

  1. investigating Oct 22, 2025, 02:30 AM UTC

    We are currently investigating a condition where customers might experience pending or failed backups on US2 environment.

  2. identified Oct 22, 2025, 11:59 AM UTC

    We've identified the issue and are now working on restarting the failed backups.

  3. resolved Oct 22, 2025, 12:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 20, 2025 AWS outage, potential service disruption 15h 56m Overall

Started Oct 20, 2025, 08:36 AM UTC· resolved Oct 21, 2025, 12:33 AM UTC

  1. investigating Oct 20, 2025, 08:36 AM UTC

    Due to an ongoing AWS outage - We're currently investigating a potential disruption to our services. We will send an additional update in 60 minutes.

  2. identified Oct 20, 2025, 09:32 AM UTC

    We've confirmed US instances are affected by the AWS outage - We're seeing failures in Jobs,Backups and Archive. Once the AWS outage resolves failed backups will be restarted.

  3. resolved Oct 21, 2025, 12:33 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 9, 2025 US2 - Users gets error 500 when attempting to login 35m Overall

Started Oct 09, 2025, 04:01 PM UTC· resolved Oct 09, 2025, 04:37 PM UTC

  1. investigating Oct 09, 2025, 04:01 PM UTC

    We are currently investigating this incident.

  2. resolved Oct 09, 2025, 04:37 PM UTC

    This incident has been resolved.

Read the full incident report →