[IEB01][Dedicated Servers] - Rack IEB0101A01B incident notification
We are pleased to inform you that the incident affecting our Dedicated Servers offering on rack IEB0101A01B has been resolved. Start time : 06/10/2026 11:00 UTC End time : 08/10/2026 08:40 UTC Root Cause : This incident was caused by a cooling system issue. We apologize for any inconvenience caused and appreciate your understanding.
The latest update from OVHcloud.
State
Resolved
Started
27 d ago
2026-10-06 11:32 UTC
Lasted
2 days
until 2026-10-08 20:11 UTC
Worst impact
Partial outage
Timeline
7 updatesIdentified
2 days 100%
Updates
Times in UTCAs posted by OVHcloud
We are pleased to inform you that the incident affecting our Dedicated Servers offering on rack IEB0101A01B has been resolved. Start time : 06/10/2026 11:00 UTC End time : 08/10/2026 08:40 UTC Root Cause : This incident was caused by a cooling system issue. We apologize for any inconvenience caused and appreciate your understanding.
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : The majority of the servers located in rack IEB0101A01B are no longer impacted by this incident. Ongoing Actions : Our teams are currently working on the last impacted servers located in the specified rack. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
Please find an update of this incident below : Update : IPMI is now operational again in the rack IEB0101A01B. Ongoing Actions : 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.
Please find an update of this incident below : Update : The vRack network is now operational again in the rack IEB0101A01B. However, some servers and IPMI remain temporarily unavailable in the specified rack. Ongoing Actions : Our teams are checking the remaining servers one by one and working to restore IPMI access as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
Please find an update of this incident below : Update : Some servers in the rack IEB0101A01B are still unavailable. The vRack network and IPMI are also temporarily unavailable in the specified rack. Impacted Service(s) : vRack network and IPMI (Intelligent Platform Management Interface) are temporarily unavailable in the rack IEB0101A01B. Customers Impact : Customers are temporarily unable to access and use their servers through vRack network. Customers are also temporarily unable to access their IPMI network, preventing remote server management such as forced reboots and console access. Ongoing Actions : Our teams are currently replacing the affected network equipment 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.
Please find an update of this incident below : Update : Some servers in the impacted rack IEB0101A01B are progressively becoming operational again. Ongoing Actions : 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 experiencing an ongoing incident. We have determined the origin of the issue affecting our Dedicated Servers offer on the specific rack IEB0101A01B. Here are some supplementary details : Start time : 06/10/2026 11:00 UTC Impacted Service(s) : All servers in the rack IEB0101A01B are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their servers located on the specified rack. Root Cause : This incident is caused by a cooling system 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.
Affected components
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
217
Days with an incident
90
Median duration
1 h 35 min
This incident
36× the median
Other OVHcloud incidents
All incidentsOVHcloud·[SBG8][Virtual Private Servers] - VPS Incident Notification
Some Virtual Private Servers in the SBG8 region were temporarily unreachable. The incident affected some VPS in the SBG region. OVHcloud identified a network equipment issue as the cause. OVHcloud resolved the incident. The incident started at 17:55 UTC and ended at 19:54 UTC.
OVHcloud·[SBG6/8][Virtual Private Servers] - VPS Incident Notification
Some Virtual Private Servers in the SBG5, SBG6 and SBG8 regions were unreachable. OVHcloud reports that the incident is resolved. It lasted from 17:55 UTC to 19:30 UTC.
OVHcloud·[RBX3][Dedicated Servers] - Rack 46E19 Incident Notification
OVHcloud reports that servers in Rack 46E19, RBX3, were not accessible through the IPMI interface. The incident was caused by a network equipment issue. The incident is resolved and it lasted 2 hours and 23 minutes.
OVHcloud·[SBG5/7][Compute - Instance] - Compute Instance Incident Notification
OVHcloud Compute Instance service did not work for some instances in the SBG5 and SBG7 regions. OVHcloud reports that the incident is resolved. The incident lasted from 17:55 UTC to 19:30 UTC.
OVHcloud·[RBX2][Dedicated Servers] - Rack 21D12 Incident Notification
We are pleased to inform you that the incident affecting our Dedicated Servers offering has been resolved. Start time : 31/10/2026 19:38 UTC End time : 31/10/2026 22:10 UTC Root Cause : This incident was caused by an electrical equipment issue. We apologize for any inconvenience caused and appreciate your understanding.
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.cc/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.cc/feed.xml?providers=ovhcloud/feed subscribe https://outages.cc/feed.xml?providers=ovhcloudFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane