[RBX8][Dedicated Servers] - Rack R809R03 incident notification
OVHcloud reports that some Dedicated Servers in rack R809R03 in the RBX region were temporarily unavailable. OVHcloud resolved the incident. The incident started at 08:33 UTC and ended at 09:05 UTC, so it lasted 32 minutes.
State
Resolved
Started
Lasted
54 min
Worst impact
Partial outage
Timeline
3 updatesInvestigating
6 min 12%
Identified
48 min 88%
Updates
Times in UTCAs posted by OVHcloud
We are pleased to inform you that the incident affecting our Dedicated Servers offering has been resolved. Start time : 16/11/2026 08:33 UTC End time : 16/11/2026 09:05 UTC Root Cause : This incident was caused by this maintenance : https://network.status-ovhcloud.com/incidents/0y9f27vs83dc We apologize for any inconvenience caused and appreciate your understanding.
The issue has been identified and a fix is being implemented.
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Dedicated Servers offer on the specific Rack R809R03. Here are some supplementary details : Start time : 16/11/2026 08:33 UTC Impacted Service(s) : Some servers in the rack R809R03 are temporarily unavailable. Customers Impact : Some customers are temporarily unable to access their servers located on the specified rack. Root Cause : This incident is caused by this maintenance : https://network.status-ovhcloud.com/incidents/0y9f27vs83dc Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. 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
46% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[RBX8][Dedicated Servers] - Rack R831A07 incident notification
OVHcloud reports that all servers in rack R831A07 in the RBX region are temporarily unavailable. This affects the Dedicated Servers offering. OVHcloud identified an electrical equipment issue as the cause. A significant number of servers in that rack are now operational.
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.
OVHcloud·[BHS/US][Infrastructure] - Backbone incident notification
OVHcloud reports packet loss and increased latency on its backbone infrastructure in the BHS and US regions. OVHcloud restored service at 02:51 UTC on 17 November 2026 and now monitors for stability. The incident started at 16:20 UTC on 16 November 2026.
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