[RBX][Public Cloud] - Compute Instance incident notification
OVHcloud reports that some Compute Instances in the RBX region are unavailable. The affected components are RBX-A and Compute - Instance RBX - RBX-A. OVHcloud is investigating the incident.
State
Investigating
Started
Ongoing for
50 min
Worst impact
Partial outage
Timeline
1 updateInvestigating
50 min 100%
Updates
Times in UTCAs posted by OVHcloud
We are currently experiencing an incident affecting our Public Cloud offering, which is causing temporary availability issues in the RBX region. Please find the details of this incident below : Start time : 17/11/2026 10:01 UTC Impacted Service(s) : Some instances in the RBX region are unavailable. Customers Impact : Some customers are temporarily unable to access their instances located in the specified region. Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
Affected components
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
232
Days with an incident
90
Median duration
1 h 40 min
This incident
50% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[US-CENTRAL-LZ-SLC][LocalZones] - Salt Lake City incident notification
OVHcloud reports a partial outage in the US-CENTRAL-LZ-SLC Local Zone. The public network and resource management are temporarily unavailable in US-CENTRAL-LZ-SLC-A. OVHcloud is investigating the origin of the incident.
OVHcloud·[RBX8][Dedicated Servers] - Rack R831A07 incident notification
OVHcloud Dedicated Servers in rack R831A07 in the RBX region did not work. Some servers were unavailable from 17/11/2026 08:18 UTC to 17/11/2026 10:23 UTC. OVHcloud reports that the incident is resolved and the cause was an electrical equipment issue.
OVHcloud·[ERI1C][Backup as a Service] - Rack ERI0111E01A - Veeam Backup Managed incident notification
OVHcloud reports that some Veeam Backup Managed storage servers were temporarily unavailable in the ERI1 region. Some customers could not run or restore their VM backups. OVHcloud reports that the incident is resolved and that it lasted about 89 minutes.
OVHcloud·[RBX3][Dedicated Servers] - Rack 41A09 incident notification
An incident affected Dedicated Servers in rack 41A09 in the RBX region. Some servers became temporarily unavailable. OVHcloud reports that the incident is resolved. It lasted from 16/11/2026 18:47 UTC to 17/11/2026 00:30 UTC. OVHcloud identified an electrical equipment issue as the cause.
OVHcloud·[RBX6][Dedicated Servers] - Rack 46N07 incident notification
OVHcloud reports that some Dedicated Servers in rack 46N07 in the RBX region were temporarily unavailable. The cause was an electrical equipment issue. The incident is resolved. It lasted from 16/11/2026 17:35 UTC to 16/11/2026 23:00 UTC.
Follow OVHcloud
Your coding agent knows when OVHcloud is down, and tells you when a failure is theirs, not yours. You can also get OVHcloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "ovhcloud" and tell me if OVHcloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=ovhcloud/feed subscribe https://outages.live/feed.xml?providers=ovhcloudFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane