OVHcloud incident

Issue affecting VPS service

Minor Resolved View vendor source →

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

Started
Oct 08, 2026, 04:19 AM UTC
Resolved
Oct 08, 2026, 06:03 AM UTC
Duration
1h 43m
Detected by Pingoru
Oct 08, 2026, 04:19 AM UTC

Affected components

Virtual Private ServicesNetwork Services (VIN)

Update timeline

  1. investigating Oct 08, 2026, 04:19 AM UTC

    We are aware of an issue affecting the VPS service. This may affect usage and/or delivery of VPS instances. 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 Oct 08, 2026, 04:19 AM UTC

    We are aware of an issue affecting the VPS service. This may affect usage and/or delivery of VPS instances. 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 Oct 08, 2026, 05:46 AM UTC

    Issue has been identified and remediation efforts have begun.

  4. identified Oct 08, 2026, 05:46 AM UTC

    Issue has been identified and remediation efforts have begun.

  5. resolved Oct 08, 2026, 06:03 AM UTC

    This issue has been resolved.