[BHS/US][Infrastructure] - Backbone incident notification
OVHcloud reports packet loss and increased latency on its backbone infrastructure in the BHS and US regions. OVHcloud restored service at 02:51 UTC on 17 November 2026 and now monitors for stability. The incident started at 16:20 UTC on 16 November 2026.
State
Monitoring
Started
Ongoing for
17 h 49 min
Worst impact
Partial outage
Timeline
7 updatesInvestigating
8 min 1%
Identified
10 h 48 min 61%
Monitoring
6 h 53 min 39%
Updates
Times in UTCAs posted by OVHcloud
We would like to inform you that our service has been fully restored as of 17/11/2026 02:51 UTC. Monitoring is still in place to ensure long-term stability. Please find the details of this incident below : Start time : 16/11/2026 16:20 UTC Impacted Service(s) : Packet loss and increased latency occurred on our backbone infrastructure. Customers Impact : Customers may have experienced packet loss and increased latency when accessing their services in the specified regions. Root Cause : This incident was caused by a fiber cut. We apologize for any inconvenience caused and appreciate your understanding.
Please find an update of this incident below : Update : The location of the fiber cut has been identified by our provider. Repair works will continue throughout the night. Ongoing Actions : In coordination with our provider, 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 have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : The situation remains unchanged since our last update. The temporary workaround is still in place and traffic between BHS and US remains stable. Ongoing Actions : Our teams remain mobilised and continue working with our provider to fully resolve the incident. We will keep you updated on the progress and resolution. 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 : Following a temporary workaround implemented by our teams, traffic between BHS and US is progressively recovering. Ongoing Actions : Our teams remain mobilised and continue working with our provider to fully resolve the incident. We will keep you updated on the progress and resolution. 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 : Following the fiber cut, several links between our US and BHS regions were lost. Traffic from BHS has been re-routed through Europe to maintain connectivity. Ongoing Actions : Our teams are working with our provider to repair the affected links. 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 Backbone offering in the BHS and US regions. The root cause has been identified. Please find the details of this incident below : Start time : 16/11/2026 16:20 UTC Impacted Service(s) : Packet loss and increased latency on our backbone infrastructure. Customers Impact : Customers may experience packet loss and increased latency when accessing their services in the specified regions. Root Cause : This incident is caused by a fiber cut. 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 Backbone offering, which is causing temporary packet loss and latency issues in the BHS and US regions. Please find the details of this incident below : Start time : 16/11/2026 [HH:MM] UTC Impacted Service(s) : Packet loss and increased latency on our backbone infrastructure. Customers Impact : Customers may experience packet loss and increased latency when accessing their services in the specified regions. 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
1OVHcloud in the last 90 days
Full historyIncidents in 90 days
232
Days with an incident
90
Median duration
1 h 40 min
This incident
11× the median
Other OVHcloud incidents
All incidentsOVHcloud·[RBX8][Dedicated Servers] - Rack R831A07 incident notification
OVHcloud reports that all servers in rack R831A07 in the RBX region are temporarily unavailable. This affects the Dedicated Servers offering. OVHcloud identified an electrical equipment issue as the cause. A significant number of servers in that rack are now operational.
OVHcloud·[ERI1C][Backup as a Service] - Rack ERI0111E01A - Veeam Backup Managed incident notification
OVHcloud reports that some Veeam Backup Managed storage servers were temporarily unavailable in the ERI1 region. Some customers could not run or restore their VM backups. OVHcloud reports that the incident is resolved and that it lasted about 89 minutes.
OVHcloud·[RBX3][Dedicated Servers] - Rack 41A09 incident notification
An incident affected Dedicated Servers in rack 41A09 in the RBX region. Some servers became temporarily unavailable. OVHcloud reports that the incident is resolved. It lasted from 16/11/2026 18:47 UTC to 17/11/2026 00:30 UTC. OVHcloud identified an electrical equipment issue as the cause.
OVHcloud·[RBX6][Dedicated Servers] - Rack 46N07 incident notification
OVHcloud reports that some Dedicated Servers in rack 46N07 in the RBX region were temporarily unavailable. The cause was an electrical equipment issue. The incident is resolved. It lasted from 16/11/2026 17:35 UTC to 16/11/2026 23:00 UTC.
OVHcloud·[RBX][Public VMware Cloud Foundation as-a-Service] - Rack RBX1003D02C
We had an incident on Public VMware Cloud Foundation offer which has now been resolved. Here are some supplementary details : Start time : 15/11/2026 23:05 UTC End time : 15/11/2026 23:20 UTC Impacted Service(s) : Some hosts in this region were temporarily unavailable. Customers Impact : Some of customer VMs might have restarted. Root Cause : This incident was caused by a cooling system 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