[LIM/FRA][Network] - Backbone Incident Notification
We had an incident on our Backbone offer which has now been resolved. Here are some supplementary details : Start time : 14/08/2026 10:18 UTC End time : 14/08/2026 10:27 UTC Impacted Service(s) : Increased network latency and packet loss affecting traffic between LIM and FRA region. Customers Impact : Customers experienced increased latency, packet loss, and degraded performance on incoming and outgoing traffic in LIM region. Root Cause : This incident was caused by a network equipment issue. We thank you for your understanding and patience throughout this incident.
The latest update from OVHcloud.
State
Resolved
Started
80 d ago
2026-08-14 11:01 UTC
Lasted
1 min
until 2026-08-14 11:01 UTC
Worst impact
Notice
Timeline
1 updateResolved
1 min 100%
Updates
Times in UTCAs posted by OVHcloud
We had an incident on our Backbone offer which has now been resolved. Here are some supplementary details : Start time : 14/08/2026 10:18 UTC End time : 14/08/2026 10:27 UTC Impacted Service(s) : Increased network latency and packet loss affecting traffic between LIM and FRA region. Customers Impact : Customers experienced increased latency, packet loss, and degraded performance on incoming and outgoing traffic in LIM region. Root Cause : This incident was caused by a network equipment issue. We thank you for your understanding and patience throughout this incident.
Affected components
1OVHcloud in the last 90 days
Full historyIncidents in 90 days
213
Days with an incident
90
Median duration
1 h 35 min
This incident
100% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[SBG8][Virtual Private Servers] - VPS Incident Notification
OVHcloud reports that some Virtual Private Servers in the SBG8 region were temporarily unreachable. OVHcloud identified the cause as a network equipment issue. The incident is resolved and lasted about 1 hour and 59 minutes.
OVHcloud·[SBG6/8][Virtual Private Servers] - VPS Incident Notification
We are pleased to inform you that the incident affecting our VPS offering has been resolved. Start time : 01/11/2026 17:55 UTC End time : 01/11/2026 19:30 UTC Root Cause : This incident was caused by a network equipment issue. We apologize for any inconvenience caused and appreciate your understanding.
OVHcloud·[RBX3][Dedicated Servers] - Rack 46E19 Incident Notification
We are pleased to inform you that the incident affecting our Dedicated Servers offering has been resolved. Start time : 01/11/2026 17:15 UTC End time : 01/11/2026 19:38 UTC Root Cause : This incident was caused by a network equipment issue. We apologize for any inconvenience caused and appreciate your understanding.
OVHcloud·[SBG5/7][Compute - Instance] - Compute Instance Incident Notification
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 01/11/2026 17:55 UTC End time : 01/11/2026 19:30 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
OVHcloud·[RBX2][Dedicated Servers] - Rack 21D12 Incident Notification
We are pleased to inform you that the incident affecting our Dedicated Servers offering has been resolved. Start time : 31/10/2026 19:38 UTC End time : 31/10/2026 22:10 UTC Root Cause : This incident was caused by an electrical equipment issue. We apologize for any inconvenience caused and appreciate your understanding.
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