Is Own down?
Last checked 4m agoNo incidents right now.
Own is operational right now. Last checked 4m ago; the most recent incident resolved 12d 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 40 incidents in the last 90 days (99.80% uptime). Get email, Slack, Discord, or webhook alerts the moment Own reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Backup & Recover
Timeline · 2 updates
- 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.
Latest: This incident has been resolved.
-
- Backup & RecoverArchiveData Mask & SeedBackup & RecoverArchiveData Mask & SeedBackup & RecoverArchiveData Mask & Seed
Timeline · 4 updates
- 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.
Latest: This incident has been resolved.
-
-
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…
-
- 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.
-
- Service disruption in CA4 Azure ResolvedStarted Aug 22, 2026, 11:00 AM UTC · Resolved Aug 22, 2026, 05:06 PM UTC · 6h 6m
- Product UI degradation ResolvedStarted Aug 04, 2026, 05:30 AM UTC · Resolved Aug 04, 2026, 11:43 AM UTC · 6h 13m
- Started Jun 21, 2026, 08:45 AM UTC · Resolved Jun 21, 2026, 08:45 AM UTC · —
- Started Jun 21, 2026, 08:45 AM UTC · Resolved Jun 21, 2026, 04:47 PM UTC · 8h 2m