[LIM/FRA][Infrastructure] - Backbone incident notification
We are currently experiencing an incident affecting our Backbone offering, which is causing temporary latency issues on the link between LIM and FRA. Please find the details of this incident below : Start time : 18/11/2026 14:55 UTC Impacted Service(s) : increased latency on our backbone infrastructure. Customers Impact : Customers may experience increased latency when accessing their services passing through LIM and FRA. 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.
The latest update from OVHcloud.
State
Investigating
Started
Ongoing for
47 min
Worst impact
Degraded
Timeline
1 updateInvestigating
47 min 100%
Updates
Times in UTCAs posted by OVHcloud
We are currently experiencing an incident affecting our Backbone offering, which is causing temporary latency issues on the link between LIM and FRA. Please find the details of this incident below : Start time : 18/11/2026 14:55 UTC Impacted Service(s) : increased latency on our backbone infrastructure. Customers Impact : Customers may experience increased latency when accessing their services passing through LIM and FRA. 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
196
Days with an incident
90
Median duration
1 h 40 min
This incident
53% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[GRA][Web Hosting] - Cluster129/Filerz956 incident notification
We are currently experiencing an incident affecting our Web Hosting offering, which is causing temporary latency issues in the Cluster129. Please find the details of this incident below : Start time : 18/11/2026 13:45 UTC Impacted Service(s) : Filerz956 is experiencing latency issues on the Cluster129. Customers Impact : Customers are temporarily experiencing latency on their websites hosted on the specified Filerz. 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.
OVHcloud·[GRA1][Dedicated Servers] - Rack G125A23 incident notification
We are currently experiencing an incident affecting our Dedicated Servers offering in the rack G125A23. The root cause has been identified. Please find the details of this incident below : Start time : 18/11/2026 13:40 UTC Impacted Service(s) : Some servers in the rack G125A23 are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their servers located on the specified rack. 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.
OVHcloud·[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.
OVHcloud·[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.
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