OVHcloud incident

VPS host outage in US-EAST-VA-2

Minor Resolved View vendor source →

OVHcloud experienced a minor incident on September 30, 2026 affecting Virtual Private Services and Network Services (VIN), lasting 35m. The incident has been resolved; the full update timeline is below.

Started
Sep 30, 2026, 03:20 PM UTC
Resolved
Sep 30, 2026, 03:56 PM UTC
Duration
35m
Detected by Pingoru
Sep 30, 2026, 03:20 PM UTC

Affected components

Virtual Private ServicesNetwork Services (VIN)

Update timeline

  1. investigating Sep 30, 2026, 03:20 PM UTC

    We are aware of an issue affecting a VPS host in this region. Some VPS instances may be unavailable or unresponsive during this time. Our teams are actively working toward a resolution, and updates will be shared as progress is made. We apologize for the inconvenience. For questions please contact our Support team for assistance: support.us.ovhcloud.com/hc/en-us/articles/115001819764-How-to-contact-OVHcloud-US-Support 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 Sep 30, 2026, 03:20 PM UTC

    We are aware of an issue affecting a VPS host in this region. Some VPS instances may be unavailable or unresponsive during this time. Our teams are actively working toward a resolution, and updates will be shared as progress is made. We apologize for the inconvenience. For questions please contact our Support team for assistance: support.us.ovhcloud.com/hc/en-us/articles/115001819764-How-to-contact-OVHcloud-US-Support

  3. identified Sep 30, 2026, 03:39 PM UTC

    This issue has been identified and our teams have started remediation efforts.

  4. identified Sep 30, 2026, 03:39 PM UTC

    This issue has been identified and our teams have started remediation efforts.

  5. resolved Sep 30, 2026, 03:56 PM UTC

    This incident has been resolved