OVHcloud incident

VPS host outage in US-EAST-VA-2

Minor Resolved View vendor source →

OVHcloud experienced a minor incident on September 29, 2026 affecting Public Cloud Services and Public Cloud Services (US-EAST-VA-2), lasting 2h 44m. The incident has been resolved; the full update timeline is below.

Started
Sep 29, 2026, 12:35 AM UTC
Resolved
Sep 29, 2026, 03:20 AM UTC
Duration
2h 44m
Detected by Pingoru
Sep 29, 2026, 12:35 AM UTC

Affected components

Public Cloud ServicesPublic Cloud Services (US-EAST-VA-2)

Update timeline

  1. investigating Sep 29, 2026, 12:35 AM 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 29, 2026, 12:35 AM 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 29, 2026, 12:54 AM UTC

    The issue has been identified and remediation efforts have begun.

  4. identified Sep 29, 2026, 12:54 AM UTC

    The issue has been identified and remediation efforts have begun.

  5. resolved Sep 29, 2026, 03:20 AM UTC

    This incident has been resolved.