[SBG5][Dedicated Servers] - Rack SBG0506B04C Incident Notification
The vRack Private Network does not work for Dedicated Servers in rack SBG0506B04C in the SBG region. OVHcloud identified the incident and states that a network equipment issue causes it. OVHcloud teams work to restore service.
State
Identified
Started
Ongoing for
35 min
Worst impact
Partial outage
Timeline
1 updateIdentified
35 min 100%
Updates
Times in UTCAs posted by OVHcloud
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Dedicated Servers offer in Rack SBG0506B04C. Here are some supplementary details : Start time : 18/11/2026 11:54 UTC Impacted Service(s) : vRack Private Network is temporarily unavailable on servers in rack SBG0506B04C. Customers Impact : Customers are temporarily unable to access their servers located in the specified rack via Vrack Private Network Root Cause : This incident is caused by a network 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
196
Days with an incident
90
Median duration
1 h 41 min
This incident
66% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[RBX][Public VMware Cloud Foundation] - Public VCFaaS Incident Notification
Public VMware Cloud Foundation as-a-Service has degraded network, management plane, compute and storage in the RBX region. Some customers can have high latency and packet loss on the vRack network. OVHcloud reports that the incident is under investigation.
OVHcloud·[RBX3][Dedicated Servers] - Rack 46G20 Incident Notification
Some Dedicated Servers in Rack 46G20 in the RBX region are temporarily unavailable. OVHcloud reported an electrical equipment issue and resolved the incident. The outage lasted 37 minutes, from 10:00 to 10:37 UTC.
OVHcloud·[US][Backbone] - Backbone Incident Notification
The OVHcloud Backbone infrastructure in the US region has packet loss and increased latency. OVHcloud reports the status as investigating. OVHcloud gives no cause, workaround, or resolution time.
OVHcloud·[GRA2][Dedicated Servers] - Rack G265B01 Incident Notification
Dedicated Servers in Rack G265B01 in the GRA region do not work. OVHcloud reports that the incident is resolved. The incident lasted from 07:48 UTC to 12:22 UTC on 18/11/2026.
OVHcloud·[Global][Collaborative Solutions] - Zimbra Incident Notification
Some Zimbra mailboxes are temporarily unavailable in OVHcloud Collaborative Solutions. Web Access, Delivery email and Operations are affected. OVHcloud has identified the incident and teams are working to restore 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.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