OVHcloud incident

Issue identified with reporting of Public Cloud Gen3 instances in Billing page

Minor Resolved View vendor source →

OVHcloud experienced a minor incident on August 27, 2026 affecting Public Cloud Services and Public Cloud Services (US-EAST-VA-1) and 1 more component, lasting 22h 27m. The incident has been resolved; the full update timeline is below.

Started
Aug 27, 2026, 03:49 PM UTC
Resolved
Aug 28, 2026, 02:17 PM UTC
Duration
22h 27m
Detected by Pingoru
Aug 27, 2026, 03:49 PM UTC

Affected components

Public Cloud ServicesPublic Cloud Services (US-EAST-VA-1)Public Cloud Services (US-WEST-OR-1)Public Cloud Services (US-EAST-VA-2)Public Cloud Services (US-WEST-OR-2)Public Cloud Services (US-CENTRAL-LZ-STL-A)Public Cloud Services (US-WEST-LZ-PHX-A)Network Services (US-EAST-LZ-ATL-A)Network Services (US-EAST-LZ-BOS-A)Network Services (US-EAST-LZ-CHI-A)

Update timeline

  1. investigating Aug 27, 2026, 03:49 PM UTC

    The Billing page in the OVHcloud Control Panel is not accurately reflecting the consumption for Gen3 instances. The engineering teams are investigating the issue. 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 Aug 27, 2026, 03:49 PM UTC

    The Billing page in the OVHcloud Control Panel is not accurately reflecting the consumption for Gen3 instances. The engineering teams are investigating the issue.

  3. monitoring Aug 27, 2026, 04:26 PM UTC

    Issue has been resolved. Teams will continue to monitor to ensure no other issues are seen.

  4. monitoring Aug 27, 2026, 04:26 PM UTC

    Issue has been resolved. Teams will continue to monitor to ensure no other issues are seen.

  5. resolved Aug 28, 2026, 02:17 PM UTC

    No new issues have been identified. Resolving the incident.