Otava incident

Mid-Michigan (MM1) OTAVA® DRaaS powered by Veeam (OCC) Service Disruption - 7/13/2026

Minor Resolved View vendor source →

Otava experienced a minor incident on July 13, 2026 affecting DRaaS powered by Veeam (OCC), lasting 21h 49m. The incident has been resolved; the full update timeline is below.

Started
Jul 13, 2026, 11:34 PM UTC
Resolved
Jul 14, 2026, 09:23 PM UTC
Duration
21h 49m
Detected by Pingoru
Jul 13, 2026, 11:34 PM UTC

Affected components

DRaaS powered by Veeam (OCC)

Update timeline

  1. investigating Jul 13, 2026, 11:34 PM UTC

    Service Impacting: Yes Description: OTAVA engineers are investigating an issue impacting DRaaS powered by Veeam (OCC) services in the Mid-Michigan (MM1) data center. The affected servers are being rebooted as part of the recovery efforts. Additional updates will be provided as more information becomes available. If you have any questions or concerns regarding this maintenance, please contact us by logging into https://support.otava.com or calling 877-740-5028, option 3.

  2. identified Jul 13, 2026, 11:34 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jul 14, 2026, 02:59 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. identified Jul 14, 2026, 03:23 AM UTC

    OTAVA engineers are investigating an issue impacting DRaaS powered by Veeam (OCC) services in the Mid-Michigan (MM1) data center. Cloud Connect jobs are currently failing, and a Severity 1 case has been opened with the vendor for further investigation.

  5. monitoring Jul 14, 2026, 07:54 AM UTC

    The majority of DRaaS-powered by Veeam (OCC) jobs in the Mid-Michigan (MM1) data center are now completing successfully. A small number of jobs continue to experience failures. OTAVA engineers are working closely with the vendor to investigate these remaining issues and restore full service. Additional updates will be provided as more information becomes available.

  6. monitoring Jul 14, 2026, 07:55 AM UTC

    We are continuing to monitor for any further issues.

  7. resolved Jul 14, 2026, 09:23 PM UTC

    This incident has been resolved.