OVHcloud incident

Rabbitmq issue affecting Public Cloud

Minor Resolved View vendor source →

OVHcloud experienced a minor incident on June 17, 2026 affecting Public Cloud Services and Public Cloud Services (US-WEST-OR-1), lasting 19h 32m. The incident has been resolved; the full update timeline is below.

Started
Jun 17, 2026, 01:04 AM UTC
Resolved
Jun 17, 2026, 08:37 PM UTC
Duration
19h 32m
Detected by Pingoru
Jun 17, 2026, 01:04 AM UTC

Affected components

Public Cloud ServicesPublic Cloud Services (US-WEST-OR-1)

Update timeline

  1. investigating Jun 17, 2026, 01:04 AM UTC

    We are aware of an issue affecting the Public Cloud infrastructure. This may affect creation of new resources and normal functioning of instances and networks. 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 Jun 17, 2026, 01:04 AM UTC

    We are aware of an issue affecting the Public Cloud infrastructure. This may affect creation of new resources and normal functioning of instances and networks. Our teams are actively working toward a resolution, and updates will be shared as progress is made. We apologize for the inconvenience.

  3. monitoring Jun 17, 2026, 01:05 AM UTC

    The rabbitmq cluster has recovered and resource creation and existing resources are functioning normally. We are monitoring the issue.

  4. monitoring Jun 17, 2026, 01:05 AM UTC

    The rabbitmq cluster has recovered and resource creation and existing resources are functioning normally. We are monitoring the issue.

  5. resolved Jun 17, 2026, 08:37 PM UTC

    The cluster has remained stable and the problematic rabbitmq node has been completely replaced. The incident is resolved.