OVHcloud incident

VIN - Network Issue - V119A10

Major Resolved View vendor source →

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

Started
Jun 03, 2026, 08:53 AM UTC
Resolved
Jun 05, 2026, 03:29 PM UTC
Duration
2d 6h
Detected by Pingoru
Jun 03, 2026, 08:53 AM UTC

Affected components

Bare Metal ServicesNetwork ServicesNetwork Services (VIN)

Update timeline

  1. investigating Jun 03, 2026, 08:53 AM UTC

    We have identified an issue affecting public traffic to services on Rack V119A10. Teams are currently taking action to migrate services to another rack to mitigate further impact to customers affected. 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 03, 2026, 08:53 AM UTC

    We have identified an issue affecting public traffic to services on Rack V119A10. Teams are currently taking action to migrate services to another rack to mitigate further impact to customers affected.

  3. identified Jun 03, 2026, 10:49 AM UTC

    We have identified an issue impacting public traffic for services hosted on Rack V119A10. We are taking action to restore services.

  4. identified Jun 03, 2026, 10:49 AM UTC

    We have identified an issue impacting public traffic for services hosted on Rack V119A10. We are taking action to restore services.

  5. monitoring Jun 03, 2026, 11:37 AM UTC

    The issue has now been resolved, and no further customer impact is currently observed.

  6. monitoring Jun 03, 2026, 11:37 AM UTC

    The issue has now been resolved, and no further customer impact is currently observed.

  7. monitoring Jun 03, 2026, 01:34 PM UTC

    No further customer impact is currently observed.

  8. monitoring Jun 03, 2026, 01:34 PM UTC

    No further customer impact is currently observed.

  9. resolved Jun 05, 2026, 03:29 PM UTC

    The issue has now been resolved, and no further customer impact is currently observed.