[RBX3][Dedicated Servers] - Rack 46N07 Incident Notification
Dedicated Servers in Rack 46N07 in the RBX region are unavailable. OVHcloud reports that the incident is resolved. The incident lasted 24 minutes, from 08:15 UTC to 08:39 UTC, and the cause was an electrical equipment issue.
State
Resolved
Started
Lasted
7 min
Worst impact
Partial outage
Timeline
2 updatesIdentified
7 min 100%
Updates
Times in UTCAs posted by OVHcloud
We are pleased to inform you that the incident affecting our Dedicated Servers offering has been resolved. Start time : 19/11/2026 08:15 UTC End time : 19/11/2026 08:39 UTC Root Cause : This incident was caused by an electrical equipment issue. 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 in Rack 46N07. Here are some supplementary details : Start time : 19/11/2026 08:15 UTC Impacted Service(s) : Some servers in Rack 46N07 are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their servers located in the specified rack. Root Cause : This incident is caused by an electrical equipment 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
184
Days with an incident
90
Median duration
1 h 46 min
This incident
93% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[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.
OVHcloud·[Global][Collaborative Solutions] - Zimbra incident notification
OVHcloud Zimbra mailbox access, webmail, email delivery, and operations had a partial outage. OVHcloud reports that the incident is resolved. It lasted 3 hours and 4 minutes, from 14:30 to 17:34 UTC.
OVHcloud·[Global][Web Hosting] - HTTP/2 incident notification
OVHcloud Web Hosting has degraded service on all Web Hosting clusters. HTTP/2 support is temporarily disabled, and sites are served over HTTP/1.1 only. OVHcloud is investigating.
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