[DE2][Virtual Private Servers] - Some VPS incident notification
Some Virtual Private Servers did not work in the DE2 region. The affected components were LIM and Virtual Private Servers Global Infrastructure - LIM. OVHcloud reports that the incident is resolved. It lasted from 08:35 UTC to 10:23 UTC on 11 November 2026.
State
Resolved
Started
Lasted
1 h 7 min
Worst impact
Partial outage
Timeline
3 updatesIdentified
1 h 7 min 100%
Updates
Times in UTCAs posted by OVHcloud
We would like to inform you that the incident affecting our Virtual Private Servers offering in the DE2 region has now been resolved. Please find the details of this incident below : Start time : 11/11/2026 08:35 UTC End time : 11/11/2026 10:23 UTC Impacted Service(s) : Some VPS in the DE2 region were temporarily unavailable. Customers Impact : Customers were temporarily unable to access their VPS located in the DE2 region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific DE2 region. Here are some supplementary details : Start time : 11/11/2026 08:35 UTC Impacted Service(s) : Some VPS are temporarily unavailable. Customers Impact : Some customers are temporarily unable to use their VPS in the DE2 region. Root Cause : A service disruption occurred due to an unexpected infrastructure failure. 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.
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific DE2 region. Here are some supplementary details : Start time : 11/11/2026 08:35 UTC Impacted Service(s) : Some VPS are temporarily unavailable. Customers Impact : Some customers are temporarily unable to use their VPS in the DE1 region. Root Cause : A service disruption occurred due to an unexpected infrastructure failure. 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
255
Days with an incident
90
Median duration
1 h 41 min
This incident
33% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[GLOBAL][Network] - API Network incident notification
OVHcloud reports that API requests on VPS services do not work correctly in the BHS, ERI, GRA, LIM, SBG, SGP, SYD, UK2, WAW, MIL, YNM, EU-WEST-LZ-MRS, US-EAST-LZ-ATL, US-EAST-LZ-DAL, US-EAST-LZ-MIA, US-EAST-LZ-NYC, US-EAST-VA, US-WEST-LZ-PAO, US-WEST-OR and EU-WEST-LZ-DLN regions. Customers can get slow responses or intermittent HTTP 500 errors. OVHcloud resolved the incident. It lasted 113 minutes.
OVHcloud·[EU/CA/MUM][Network] - API Network incident notification
OVHcloud API requests on the public cloud did not work in the BHS, DE, GRA, RBX, SBG, SGP, SYD, and UK regions. The US region was not affected. OVHcloud reports that the incident is resolved. It lasted 2 hours and 9 minutes.
OVHcloud·[DE1][Compute - Instance] - Some instances incident notification
Some Compute instances in the DE1 region did not work. OVHcloud reports that the incident is resolved. The incident lasted from 08:35 UTC to 10:23 UTC.
OVHcloud·[CHI/BHS][Backbone] - Backbone incident notification
We had an incident on Backbone offer which has now been resolved. Here are some supplementary details : Start time : 11/11/2026 05:40 UTC End time : 11/11/2026 06:40 UTC Impacted Service(s) : Network traffic experienced temporary latency between BHS and CHI. Customers Impact : Customers may have temporarily experienced network latency between CHI and BHS. Root Cause : This incident was caused by a network equipment issue. We thank you for your understanding and patience throughout this incident.
OVHcloud·[RBX3][Dedicated Servers] - Rack 45D38 Incident Notification
The Public Network in Rack 45D38 is unavailable. This affects Dedicated Servers in the RBX region. OVHcloud reports that the incident is resolved. It lasted about 3 hours.
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