OVHcloud incident

Issue affecting VPS in US-EAST-VA-2

Minor Resolved View vendor source →

OVHcloud experienced a minor incident on July 31, 2026 affecting Virtual Private Services and Network Services (VIN), lasting 15h 4m. The incident has been resolved; the full update timeline is below.

Started
Jul 31, 2026, 02:20 AM UTC
Resolved
Jul 31, 2026, 05:25 PM UTC
Duration
15h 4m
Detected by Pingoru
Jul 31, 2026, 02:20 AM UTC

Affected components

Virtual Private ServicesNetwork Services (VIN)

Update timeline

  1. investigating Jul 31, 2026, 02:20 AM UTC

    We are aware of an issue affecting the VPS service in US-EAST-VA-2. Attempting to reboot or take other actions that change the state of a VPS may result in the instance becoming unresponsive. Our teams are actively working toward a resolution, and updates will be shared as progress is made. We apologize for the inconvenience. 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 Jul 31, 2026, 02:20 AM UTC

    We are aware of an issue affecting the VPS service in US-EAST-VA-2. Attempting to reboot or take other actions that change the state of a VPS may result in the instance becoming unresponsive. Our teams are actively working toward a resolution, and updates will be shared as progress is made. We apologize for the inconvenience.

  3. investigating Jul 31, 2026, 02:50 AM UTC

    This issue is specific to VPS instances with an additional disk attached.

  4. investigating Jul 31, 2026, 02:50 AM UTC

    This issue is specific to VPS instances with an additional disk attached.

  5. identified Jul 31, 2026, 03:25 AM UTC

    We have identified an issue with one of our storage clusters and our teams are working on a fix. This issue is also intermittently impacting creation of new additional disks in this region.

  6. identified Jul 31, 2026, 03:25 AM UTC

    We have identified an issue with one of our storage clusters and our teams are working on a fix. This issue is also intermittently impacting creation of new additional disks in this region.

  7. identified Jul 31, 2026, 04:33 AM UTC

    The solution is in progress and will take roughly 2 hours complete.

  8. identified Jul 31, 2026, 04:33 AM UTC

    The solution is in progress and will take roughly 2 hours complete.

  9. monitoring Jul 31, 2026, 06:20 AM UTC

    The affected instances are now operating as expected and volumes can be created normally, we are monitoring the issue.

  10. monitoring Jul 31, 2026, 06:20 AM UTC

    The affected instances are now operating as expected and volumes can be created normally, we are monitoring the issue.

  11. resolved Jul 31, 2026, 05:25 PM UTC

    This issue has been resolved.