Is Own down?

Last checked 6m ago
Current status
Own is up

No incidents right now.

Official status page: https://status.owndata.com · Polled every 5 minutes · 67 components tracked

Own is operational right now. Last checked 6m ago; the most recent incident resolved 5d ago.

Real-time Own status, recent outages, and incident history — pulled directly from Own's official status page at https://status.owndata.com every 5 minutes. Pingoru tracks 67 Own services and has captured 66 incidents in the last 90 days (99.85% uptime). Get email, Slack, Discord, or webhook alerts the moment Own reports a new incident — free for 5 monitors, no credit card.

Users who monitor Own also follow these Backup services: Carbonite CrashPlan Druva inSync Druva Phoenix Jungle Disk Rewind Slide Jatheon View all 6,000+ providers
Own uptime 99.85% uptime · past 90 days
Mon Wed Fri
MayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Jun 21, 2026, 08:45 AM UTC · Resolved Jun 21, 2026, 08:45 AM UTC
    Timeline · 1 update
    • resolved · Jun 21, 2026, 08:45 AM UTC

      Type: Incident Duration: 8 hours and 3 minutes Affected Components: Archive Jun 21, 08:45:00 GMT+0 - Investigating - We are currently investigating this incident. Customers may experience high latency while using Archive on Azure CA4 Jun 21, 11:04:00 GMT+0 - Investigating - We're currently experiencing an issue affecting the Archive service. Customers may be unable to search archived data, and the UI for accessing and managing archive policies is unavailable. We are continuing to work on a fix for this incident Jun 21, 16:25:39 GMT+0 - Monitoring - The incident has been resolved. We are closely monitoring the service to verify its full recovery. Jun 21, 16:47:44 GMT+0 - Resolved - This incident has been resolved.

    Latest: Type: Incident Duration: 8 hours and 3 minutes Affected Components: Archive Jun 21, 08:45:00 GMT+0 - Investigating - We are currently investigating this incident. Customers may exp…

  2. Resolved 8h 2m
    Started Jun 21, 2026, 08:45 AM UTC · Resolved Jun 21, 2026, 04:47 PM UTC
    Archive
    Timeline · 4 updates
    • 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.

    Latest: This incident has been resolved.

  3. Resolved
    Started Jun 15, 2026, 07:30 AM UTC · Resolved Jun 15, 2026, 07:30 AM UTC
    Timeline · 1 update
    • resolved · Jun 15, 2026, 07:30 AM UTC

      Type: Maintenance Duration: 3 hours Affected Components: Data Mask & Seed, Backup & Recover, Data Mask & Seed, Data Mask & Seed, Backup & Recover, Salesforce Discover, Salesforce Discover, Backup & Recover, Data Mask & Seed, Backup & Recover, Salesforce Discover Jun 10, 15:17:25 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Jun 15, 07:30:01 GMT+0 - Identified - Maintenance is now in progress Jun 15, 10:30:00 GMT+0 - Completed - Maintenance has completed successfully

    Latest: Type: Maintenance Duration: 3 hours Affected Components: Data Mask & Seed, Backup & Recover, Data Mask & Seed, Data Mask & Seed, Backup & Recover, Salesforce Discover, Salesforce D…

  4. Resolved
    Started Jun 10, 2026, 09:30 AM UTC · Resolved Jun 10, 2026, 09:30 AM UTC
    Timeline · 1 update
    • resolved · Jun 10, 2026, 09:30 AM UTC

      Type: Maintenance Duration: 3 hours Affected Components: Backup & Recover, Salesforce Discover, Data Mask & Seed, Salesforce Discover, Backup & Recover, Data Mask & Seed Jun 10, 09:30:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Jun 10, 09:30:01 GMT+0 - Identified - Maintenance is now in progress Jun 10, 12:30:00 GMT+0 - Completed - Maintenance has completed successfully

    Latest: Type: Maintenance Duration: 3 hours Affected Components: Backup & Recover, Salesforce Discover, Data Mask & Seed, Salesforce Discover, Backup & Recover, Data Mask & Seed Jun 10, 09…

  5. Resolved
    Started May 29, 2026, 05:04 AM UTC · Resolved May 29, 2026, 05:04 AM UTC
    Timeline · 1 update
    • 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.

    Latest: 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…

See the full Own outage history

3 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Own outage history →

Or sign up free to get alerts when Own breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 8 incidents View full outage history →