Vendor Status Watch

← all vendors

Otava status history

Current state: operational — “All Systems Operational” per https://status.otava.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

6incidents, last 30 days
20incidents, last 90 days
49incidents on record
Incidents per week, last 12 weeks:

How long do Otava incidents last?

2.2 daysmedian incident duration46 measured
13.8 days90th percentile1 in 10 ran longer
39.2 hmedian, major/critical only22 incidents

From 46 incidents with a vendor-posted start and resolve time. Longest on record: Austin (AU1) – Internet Instability – October 31, 2025 — 63.2 days (2025-10-31 15:26 UTC). Excluded, never estimated: 3 scheduled maintenance. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (49)

StartedIncidentStatusImpactDuration
2026-09-14 06:00 UTCOTMonitor Collectors Server Patching - 9/14/2026maintenancemaintenance30 h 28 min (approx.)
2026-09-10 05:00 UTCDenver (DEN2) OTAVA® VMs Patching in Denver vCenter - 9/10/2026maintenancemaintenance31 h 29 min (approx.)
2026-09-09 16:14 UTCPhoenix (PHX) OTAVA® Cloud Backup (OCB), Service Degraded - 9/9/2026resolvedmajor23 h 39 min
2026-09-09 09:41 UTCDenver (DEN2) OTAVA® DRaaS powered by Veeam (OCC) Service Degraded - 9/9/2026resolvedmajor27 h 08 min
2026-09-09 07:00 UTCMid-Michigan (MM) OTAVA® vCenter patching - 9/9/2026maintenancemaintenance29 h 15 min (approx.)
2026-09-07 14:51 UTCMid-Michigan (MM1) - Internet Connectivity Degradation - 9/7/2026resolvedminor47 h 09 min
2026-08-12 16:11 UTCMid-Michigan (MM1) OTAVA® Data Center Networking Infrastructure Major Service Disruption – 08/12/2026resolvednone24 h 25 min
2026-08-03 16:48 UTCAshburn (AB1) Router loss of redundancy - 07/30/2026resolvednone9 d 6 h
2026-07-26 09:54 UTCIndianapolis (IN1) Management Connectivity Issues on GEN3 DRaaS powered by Veeam - 7/26/2026resolvedmajor2 d 3 h
2026-07-19 16:06 UTCAU (SC1) vCloud Degradationresolvedminor3 d 3 h
2026-07-18 14:27 UTCOTAVA® Mid-Michigan (MM1) Data Center Utility Power Interruption - 7/18/26resolvednone24 h 45 min
2026-07-17 15:05 UTCPhoenix (PHX1) OTAVA® Private Cloud vCD Management Access Disruption - 7/17/2026resolvedmajor1 h 18 min
2026-07-15 21:03 UTCIndianapolis (IN1) OTAVA® Backup for Microsoft 365 (VBO) - Degraded Performanceresolvedminor17 h 01 min
2026-07-15 15:16 UTCAnn Arbor (AA2) OTAVA® Data Center Networking Infrastructure Degradationresolvedminor12 d 4 h
2026-07-13 23:34 UTCMid-Michigan (MM1) OTAVA® DRaaS powered by Veeam (OCC) Service Disruption - 7/13/2026resolvedminor21 h 49 min
2026-07-03 23:12 UTCMetro-Detroit (MD1)- Utility Power Disruption - 7/3/2026resolvednone2 d 18 h
2026-06-30 08:56 UTCIndianapolis (IN1) Management Connectivity Issues on GEN3 DPaaS - 6/30/2026resolvedmajor10 h 41 min
2026-06-29 17:15 UTCDenver (DEN2) - Otava® Cloud Infrastructure - Compute IOM - 06/29/2025resolvedminor6 d 22 h
2026-06-24 23:40 UTCAshburn (VA4) to Austin (AU1) - Loss of Redundancy - 06/24/2026resolvednone2 d 1 h
2026-06-24 16:48 UTCAnn Arbor (AA2) Internet connection loss of redundancy - 06/24/2026resolvednone2 d 8 h
2026-06-10 18:29 UTCAustin (AU1) to Las Vegas (NV1) Transport Circuit lost of redundancy - 06/10/2026resolvednone5 d 2 h
2026-06-10 16:59 UTCDenver (DEN2) OTAVA® DRaaS powered by Veeam (OCC) Outage - 6/10/2026resolvedcritical4 d 21 h
2026-06-05 19:20 UTCMid-Michigan(MM1) - Internet Connectivity Degradation - 6/5/2026resolvedminor13 d 18 h
2026-06-03 21:29 UTCMid-Michigan(MM1) - Internet Connectivity Degradation - 6/3/2026resolvedmajor15 h 22 min
2026-05-27 14:39 UTCDenver (DEN2) OTAVA® DRaaS powered by Veeam (OCC) Service Partial Outage - 5/27/2026resolvedmajor5 d 22 h
2026-05-27 13:25 UTCAU (AU-PUBVC2) - Host Failure - 5/27/2026resolvedminor5 h 04 min
2026-05-20 20:36 UTCDenver (DEN2) OTAVA® DRaaS powered by Veeam (OCC) Veeam Service Provider Console (VSPC) Service Degraded - 5/20/2026resolvedminor6 d 17 h
2026-05-13 23:49 UTCMM1 - Internet Connectivity Degradation - 5/13/2026postmortemmajor4 d 20 h
2026-04-22 13:59 UTCOTAVA® Encore (portal.otava.com) Outage - 4/22/2026resolvedminor2 h 31 min
2026-04-15 18:56 UTCOTAVA® Managed Endpoint (Automate) Emergency Maintenance - 4/15/2026resolvedmajor38 min
2026-04-07 15:15 UTCIndianapolis (IN1) OTAVA® Backup for Microsoft 365 (VBO) - Partial Outageresolvedmajor2 d 23 h
2026-03-20 13:30 UTCAustin (AU1) OTAVA Monitoring Interruption - 3/20/26resolvedmajor10 h 54 min
2026-03-18 10:39 UTCDenver OCC Jobs Failingresolvedmajor21 h 15 min
2026-03-13 17:29 UTCMetro Detroit (MD1) Data Center Utility Outage - 3/13/26resolvednone43 h 56 min
2026-01-26 23:21 UTCLas Vegas (LV) OCC Interruptionresolvedmajor22 d 15 h
2026-01-25 18:35 UTCAustin (AU) OCB Veeam Disruptionresolvedmajor7 d 13 h
2026-01-25 03:30 UTCAustin (AU) OCB Veeam Disruptionresolvedminor0 min
2026-01-20 12:21 UTCManagement Network Connectivity Issues – Ashburn Data Centerresolvedminor7 d 0 h
2026-01-02 21:07 UTCAustin (AU1) – Internet Instability – 1/2/26resolvedminor41 d 0 h
2025-12-17 19:24 UTCDEN OCC VSPC - Degraded Performanceresolvednone22 h 28 min
2025-12-01 07:09 UTCMM1 - Flint, MI (Mid-Michigan) OTAVA Cloud Backupresolvednone4 d 1 h
2025-11-20 16:41 UTCIndianapolis (IN1) Backup for Microsoft 365 Critical Maintenance – 11/20/25resolvedcritical15 d 4 h
2025-11-18 14:07 UTCAustin (AU1), Las Vegas (NV1), Indianapolis (IN1) VCD, Mid-Michigan (MM1) OTAVA® Shared + Private Cloud VCD and Encore Major Outage - 11/18/25resolvedcritical3 h 55 min
2025-10-31 15:26 UTCAustin (AU1) – Internet Instability – October 31, 2025resolvedminor63 d 5 h
2025-10-14 21:24 UTCOTAVA® Managed Endpoint (Automate) Outage – 10/14/2025resolvedmajor23 h 57 min
2025-10-14 06:49 UTCReplication Issues between MM and IN1resolvedmajor14 d 7 h
2025-10-10 12:00 UTCDenver OCB Partial Outageresolvedmajor3 d 8 h
2025-10-06 16:01 UTCMid-Michigan (MM1) DRaaS Powered by Zerto Service Interruption - 10/6/25resolvedmajor3 h 58 min
2025-09-10 07:29 UTCAB | OCB Backup jobs are failing - Investigatingresolvedcritical9 d 4 h

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Otava with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "otava"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}