[BHS1][Dedicated Servers] - Rack T01C28 incident notification
OVHcloud reports a partial outage of Dedicated Servers public network in rack T01C28 in the BHS region. Since 03:15 UTC, the public network in this rack is unavailable. OVHcloud identified a network equipment issue and its teams work to restore service.
State
Identified
Started
Ongoing for
32 min
Worst impact
Partial outage
Timeline
2 updatesInvestigating
26 min 80%
Identified
6 min 20%
Updates
Times in UTCAs posted by OVHcloud
We are currently experiencing an incident affecting our Dedicated Servers offering in the rack T01C28. The root cause has been identified. Please find the details of this incident below : Start time : 10/11/2026 02:28 UTC Impacted Service(s) : Since 03:15 UTC, public network is temporarily unavailable in the specified rack. Customers Impact : Customers are temporarily unable to access and use their servers through public 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.
We are currently experiencing an incident affecting our Dedicated Servers offering, which is causing temporary availability issues in the rack T01C28. Please find the details of this incident below : Start time : 10/11/2026 02:28 UTC Impacted Service(s) : Public network is temporarily degraded in the specified rack. Customers Impact : Customers may experience disruptions when accessing their servers through public 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
246
Days with an incident
90
Median duration
1 h 39 min
This incident
68% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[Global][Collaborative Solutions] - Zimbra incident notification
OVHcloud reports that access to Zimbra mailboxes and webmail was unavailable. The affected components are Web Access and Zimbra Web Access. OVHcloud says the incident is resolved, and it lasted about 53 minutes.
OVHcloud·[Global][Collaborative Solutions] - Zimbra Incident Notification
OVHcloud reports slow delivery to some Zimbra mailboxes and webmail accounts. The incident affects the Zimbra Delivery email component. OVHcloud identified the root cause and its teams are working to restore service. Incoming emails are queued.
OVHcloud·[GLOBAL][Domains] - .DK Domain Names Incident Notification
OVHcloud reports that multiple operations on .DK domain names do not work. Registration, Renew, Transfer, Restore, and Delete are affected for .DK domain names. OVHcloud identified the root cause and teams are working to restore service.
OVHcloud·[FR][Collaborative Solutions] - Zimbra Incident Notification
OVHcloud Zimbra Web Access, Delivery email, and Operations have a partial outage in France. Access to some mailboxes and webmail is unavailable, and incoming emails are queued. OVHcloud reports the incident resolved. The incident lasted from 07:10 UTC to 16:30 UTC on 09/11/2026.
OVHcloud·[GRA2][Dedicated Servers] - Rack G243A16 incident notification
We had an incident on Dedicated Servers offer which has now been resolved. Here are some supplementary details : Start time : 07/11/2026 10:32 UTC End time : 07/11/2026 13:50 UTC Impacted Service(s) : Servers in the rack were no longer able to access the vRack network. Customers Impact : Customers were temporarily unable to access their servers via public and vRack networks located on the specified rack. Root Cause : This incident was caused by a network equipment issue. We thank you for your understanding and patience throughout this incident.
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