[RBX5][Dedicated Servers] - Rack 45D18 incident notification
The vRack network is unavailable for Dedicated Servers in rack 45D18 in the RBX region. OVHcloud reports that the incident is identified and that a network equipment issue is the cause. OVHcloud teams work to restore service.
State
Identified
Started
Ongoing for
1 h 7 min
Worst impact
Partial outage
Timeline
1 updateIdentified
1 h 7 min 100%
Updates
Times in UTCAs posted by OVHcloud
We are currently experiencing an incident affecting our Dedicated Servers offering in the rack 45D18. The root cause has been identified. Please find the details of this incident below : Start time : 20/11/2026 08:07 UTC Impacted Service(s) : vRack network is temporarily unavailable in the rack 45D18. Customers Impact : Customers are temporarily unable to access and use their servers through vRack network. Root Cause : This incident is caused by a network equipment issue. Ongoing Actions : Our teams are actively working 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
180
Days with an incident
90
Median duration
1 h 45 min
This incident
36% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[EU/US/APAC][Infrastructure] - Backbone incident notification
OVHcloud reports packet loss on some backbone links between Europe and APAC, and between North America and APAC. The incident is resolved. OVHcloud gives the start time as 08:15 UTC and the end time as 09:15 UTC on 20/11/2026.
OVHcloud·[GLOBAL][AI & Machine Learning] - AI Endpoint Incident Notification
The AI Endpoint component of OVHcloud AI & Machine Learning has a partial outage. OVHcloud reports that the service was fully restored at 07:12 UTC on 20/11/2026 and that monitoring is in place. The incident started at 06:25 UTC.
OVHcloud·[Global][Identity, Security & Operations] - Logs Data Platform incident notification
We would like to inform you that the incident affecting our Identity, Security & Operations offering has now been resolved. Please find the details of this incident below : Start time : 19/11/2026 17:31 UTC End time : 19/11/2026 20:50 UTC Impacted Service(s) : The OpenSearch API of the Logs Data Platform service was temporarily unavailable. Customers Impact : Customers were temporarily unable to query or access their logs through the OpenSearch API. Log ingestion remained unaffected. Root Cause : This incident was caused by a network equipment issue. We thank you for your understanding and patience throughout this incident.
OVHcloud·[US-WEST-OR][Storage] - Cloud Archive incident notification
The Cloud Archive service in the US-WEST-OR region has an increased error rate. Storing or retrieving archived data may fail. OVHcloud reports the root cause as identified.
OVHcloud·[BHS-CHI][Infrastructure] - Backbone incident notification
OVHcloud reports increased latency on the Backbone link between BHS and CHI. OVHcloud states that the incident is resolved. The incident lasted from 19:41 UTC to 20:38 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