[RBX3][Dedicated Servers] - Rack 45D38 Incident Notification
The Public Network in Rack 45D38 is unavailable. This affects Dedicated Servers in the RBX region. OVHcloud reports that the incident is resolved. It lasted about 3 hours.
State
Resolved
Started
Lasted
2 h 52 min
Worst impact
Partial outage
Timeline
3 updatesInvestigating
22 min 13%
Identified
2 h 31 min 87%
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 : 10/11/2026 18:13 UTC End time : 10/11/2026 21:15 UTC Root Cause : This incident was caused by a Network equipment issue. We apologize for any inconvenience caused and appreciate your understanding.
We have determined the origin of the issue affecting our Dedicated Servers offer in Rack 45D38. Here are some supplementary details : Start time : 10/11/2026 18:13 UTC Impacted Service(s) : Public Network in Rack 45D38 is temporarily unavailable. Customers Impact : Customers are temporarily unable to access their servers located in the specified rack via Public Network. Root Cause : This incident is caused by a Network equipment issue. 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.
We are currently investigating an incident affecting our Dedicated Servers offering, which is causing temporary availability issue in Rack 45D38. Here are some supplementary details : Start time : 10/11/2026 18:13 UTC Impacted Service(s) : Servers in Rack 45D38 are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their servers located in the specified rack. Ongoing Actions : Our teams are investigating to determine the origin of the incident and 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
251
Days with an incident
90
Median duration
1 h 41 min
This incident
1.7× the median
Other OVHcloud incidents
All incidentsOVHcloud·[RBX7][Dedicated Servers] - Rack R715B08 incident notification
OVHcloud reports that the public network did not work for Dedicated Servers in rack R715B08 in the RBX region. OVHcloud identified the cause as a network equipment issue. OVHcloud resolved the incident, which lasted 26 minutes.
OVHcloud·[US][Infrastructure] - Backbone incident notification
OVHcloud reports that its backbone infrastructure in the US region had increased latency and packet loss. OVHcloud says the incident is resolved. It lasted 2 hours and 8 minutes, from 06:22 UTC to 08:30 UTC.
OVHcloud·[SGP1][Dedicated Servers] - Rack 040816B incident notification
The public network does not work for OVHcloud Dedicated Servers in rack 040816B in the SGP region. OVHcloud reports that this incident is resolved. The outage lasted 15 minutes, from 06:54 UTC to 07:09 UTC. A network equipment issue caused the incident.
OVHcloud·[RBX8][Dedicated Servers] - Rack R809R07 incident notification
OVHcloud reports that some Dedicated Servers in rack R809R07 in the RBX region did not work. OVHcloud identified an electrical equipment issue. OVHcloud resolved the incident, which lasted 3 hours and 7 minutes.
OVHcloud·[BHS1][Dedicated Servers] - Rack T01C28 incident notification
The public network does not work for Dedicated Servers in rack T01C28 in the BHS region. OVHcloud reports that this incident is resolved. It lasted from 02:28 UTC to 06:12 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