[LIM3][Dedicated Servers] - Rack LIM0302B02A incident notification
The vRack network is temporarily unavailable in rack LIM0302B02A in the LIM region. This affects Dedicated Servers network in LIM. OVHcloud has identified the cause. OVHcloud reports that a cooling system issue caused the incident and that teams are working to restore service.
State
Identified
Started
Ongoing for
55 min
Worst impact
Partial outage
Timeline
2 updatesInvestigating
6 min 10%
Identified
50 min 90%
Updates
Times in UTCAs posted by OVHcloud
We are currently experiencing an incident affecting our Dedicated Servers offering in the rack LIM0302B02A. The root cause has been identified. Please find the details of this incident below : Start time : 15/11/2026 20:39 UTC Impacted Service(s) : vRack network is temporarily unavailable in the specified rack. Customers Impact : Customers are temporarily unable to access and use their servers through vRack network. Root Cause : This incident is caused by a cooling system 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.
We are currently experiencing an incident affecting our Dedicated Servers offering, which is causing temporary availability issues in the rack LIM0302B02A. Please find the details of this incident below : Start time : 15/11/2026 20:39 UTC Impacted Service(s) : vRack network is temporarily unavailable in the specified rack. Customers Impact : Customers are temporarily unable to access and use their servers through vRack network. 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
260
Days with an incident
90
Median duration
1 h 41 min
This incident
45% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[RBX3][Dedicated Servers] - Rack 46N07 incident notification
An OVHcloud incident affected Dedicated Servers in rack 46N07 in the RBX region. All servers in that rack were temporarily unavailable. OVHcloud reports that the incident is resolved. The outage lasted about 32 minutes. The cause was an electrical equipment issue.
OVHcloud·[RBX8][Dedicated Servers] - Rack RBX0840B05B incident notification
OVHcloud reports that the vRack network did not work for Dedicated Servers in rack RBX0840B05B in the RBX region. OVHcloud identified a cooling system issue as the cause. OVHcloud resolved the incident, which lasted 2 hours and 1 minute.
OVHcloud·[RBX8][Dedicated Servers] - Rack R820R14 incident notification
All servers in rack R820R14 were temporarily unavailable. The incident affected Dedicated Servers in the RBX region. OVHcloud reports that the incident is resolved. It lasted about 3 hours and 29 minutes and was caused by a cooling system issue.
OVHcloud·[BHS][Virtual Private Servers] - VPS incident notification
Some Virtual Private Servers in the BHS region did not work. OVHcloud states that the incident is resolved. The incident lasted from 06:34 UTC to 07:07 UTC.
OVHcloud·[BHS1/3/5][Public Cloud] - Compute Instance incident notification
OVHcloud reports that some Compute instances were unavailable in the BHS1, BHS3, and BHS5 regions. OVHcloud identified the cause and worked on a fix. The incident is resolved and lasted 33 minutes, from 06:34 UTC to 07:07 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