[BHS5][Dedicated Servers] - Racks T05B28, T05B29 incident notification
OVHcloud reports that some Dedicated Servers in racks T05B28 and T05B29 in BHS5 were temporarily unavailable. OVHcloud states that the incident is resolved. It lasted about 60 minutes.
State
Resolved
Started
1 h ago
2026-11-03 07:13 UTC
Lasted
48 min
until 2026-11-03 08:01 UTC
Worst impact
Partial outage
Timeline
6 updatesIdentified
48 min 100%
Updates
Times in UTCAs posted by OVHcloud
We are currently experiencing an incident affecting our Dedicated Servers offering in the racks T05B28 and T05B29 in BHS5. The root cause has been identified. Please find the details of this incident below : Start time : 03/11/2026 07:01 UTC Impacted Service(s) : Some servers in the racks T05B28 and T05B29 are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their servers located on the specified racks. 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 would like to inform you that the incident affecting our Dedicated Servers offering has now been resolved. Please find the details of this incident below : Start time : 03/11/2026 07:01 UTC End time : 03/11/2026 08:01 UTC Impacted Service(s) : Some servers in the racks T05B28 and T05B29 were temporarily unavailable. Customers Impact : Customers were temporarily unable to access their servers located on the specified racks. Root Cause : This incident was caused by a cooling system issue. We thank you for your understanding and patience throughout this incident.
We would like to inform you that the incident affecting our Dedicated Servers offering has now been resolved. Please find the details of this incident below : Start time : 03/11/2026 07:01 UTC End time : 03/11/2026 08:01 UTC Impacted Service(s) : Some servers in the racks T05B28 and T05B29 were temporarily unavailable. Customers Impact : Customers were temporarily unable to access their servers located on the specified racks. Root Cause : This incident was caused by a cooling system issue. We thank you for your understanding and patience throughout this incident.
We are currently experiencing an incident affecting our Dedicated Servers offering in the racks T05B28 and T05B29 in BHS5. The root cause has been identified. Please find the details of this incident below : Start time : 03/11/2026 07:01 UTC Impacted Service(s) : Some servers in the racks T05B28 and T05B29 are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their servers located on the specified racks. 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 in the racks T05B27, T05B28 and T05B29 in BHS5. The root cause has been identified. Please find the details of this incident below : Start time : 03/11/2026 07:01 UTC Impacted Service(s) : Some servers in the racks T05B27, T05B28 and T05B29 are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their servers located on the specified racks. 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 in the racks T05B27 and T05B28 in BHS5. The root cause has been identified. Please find the details of this incident below : Start time : 03/11/2026 07:01 UTC Impacted Service(s) : Some servers in the racks T05B27 and T05B28 are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their servers located on the specified racks. 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.
Affected components
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
225
Days with an incident
90
Median duration
1 h 37 min
This incident
50% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[RBX8][Dedicated Servers] - Rack R809R19 Incident Notification
OVHcloud reports that Dedicated Servers in Rack R809R19 in the RBX region were temporarily unavailable. OVHcloud reports that the incident is resolved. The incident lasted from 03:33 UTC to 04:49 UTC. OVHcloud states the cause was an electrical equipment issue.
OVHcloud·[DE1][Network] - Public network incident notification
OVHcloud reports that public network management operations were unstable in the DE1 region. Customers had errors or delays when they created or changed the network configuration of their instances. OVHcloud resolved the incident, which lasted from 09:22 UTC to 18:32 UTC.
OVHcloud·[Global][Domains] - .TOP Domains Name incident notification
The .TOP domain operations do not work. Registration, Renew, Transfer, Restore, and Delete are affected. OVHcloud reports that it identified the cause. The cause is from a provider. OVHcloud works with the provider to restore service.
OVHcloud·[SBG5][Dedicated Servers] - Rack SBG0505B05B incident notification
OVHcloud reports that some Dedicated Servers in rack SBG0505B05B in the SBG region were temporarily unavailable. OVHcloud identified the cause and resolved the incident. The incident lasted from 09:50 UTC to 12:42 UTC on 02/11/2026.
OVHcloud·[Global][Domains] - .MG Domains Name incident notification
The .MG domain service does not work for Registration, Renew, Transfer, Restore, and Delete operations. OVHcloud has identified the incident. The cause comes from a provider, and OVHcloud teams work to restore the service.
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