OVHcloud incident

Network issues in the (DC) DataCenter - Rack V119E22

Major Resolved View vendor source →

OVHcloud experienced a major incident on June 28, 2026 affecting Bare Metal Services and Private Cloud Services and 1 more component, lasting 1d 4h. The incident has been resolved; the full update timeline is below.

Started
Jun 28, 2026, 07:36 AM UTC
Resolved
Jun 29, 2026, 12:18 PM UTC
Duration
1d 4h
Detected by Pingoru
Jun 28, 2026, 07:36 AM UTC

Affected components

Bare Metal ServicesPrivate Cloud ServicesNetwork Services (VIN)

Update timeline

  1. investigating Jun 28, 2026, 07:36 AM UTC

    OVHcloud Incident Please be advised that OVHcloud is aware of an issue affecting some servers in the following locations: V119E22 Impacted: • At least one or more servers in rack V119E22 are currently noticing service disruption on the private network. Additional Information and Support: • If you experience any additional issues during this time, Please contact OVH Support --> https://support.us.ovhcloud.com/hc/en-us Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close

  2. investigating Jun 28, 2026, 07:36 AM UTC

    OVHcloud Incident Please be advised that OVHcloud is aware of an issue affecting some servers in the following locations: V119E22 Impacted: • At least one or more servers in rack V119E22 are currently noticing service disruption on the private network. Additional Information and Support: • If you experience any additional issues during this time, Please contact OVH Support --> https://support.us.ovhcloud.com/hc/en-us

  3. investigating Jun 28, 2026, 07:40 AM UTC

    Private network/vrack is impacted

  4. investigating Jun 28, 2026, 07:40 AM UTC

    Private network/vrack is impacted

  5. identified Jun 28, 2026, 08:25 AM UTC

    The issue is identified and our teams are working to restore vrack connectivity as soon as possible.

  6. identified Jun 28, 2026, 08:25 AM UTC

    The issue is identified and our teams are working to restore vrack connectivity as soon as possible.

  7. monitoring Jun 28, 2026, 08:50 AM UTC

    Connectivity for the vrack is now restored. We will be monitoring for any subsequent events.

  8. monitoring Jun 28, 2026, 08:50 AM UTC

    Connectivity for the vrack is now restored. We will be monitoring for any subsequent events.

  9. identified Jun 28, 2026, 11:21 AM UTC

    Some vrack services could still be seeing impact. Our teams are continuing to troubleshoot.

  10. identified Jun 28, 2026, 11:21 AM UTC

    Some vrack services could still be seeing impact. Our teams are continuing to troubleshoot.

  11. monitoring Jun 28, 2026, 11:40 AM UTC

    Connectivity for the vrack has now been restored

  12. monitoring Jun 28, 2026, 11:40 AM UTC

    Connectivity for the vrack has now been restored

  13. resolved Jun 29, 2026, 12:18 PM UTC

    No further disruptions were detected.