[SBG5/7][Compute - Instance] - Compute Instance Incident Notification
OVHcloud Compute Instance service did not work for some instances in the SBG5 and SBG7 regions. OVHcloud reports that the incident is resolved. The incident lasted from 17:55 UTC to 19:30 UTC.
State
Resolved
Started
3 h ago
2026-11-01 17:56 UTC
Lasted
1 h 45 min
until 2026-11-01 19:41 UTC
Worst impact
Partial outage
Timeline
3 updatesIdentified
1 h 45 min 100%
Updates
Times in UTCAs posted by OVHcloud
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.
We have new information regarding the incident that affects your service(s). Please find below an update on the situation : Update : Some instances in the SBG7 region are temporarily unreachable as well. 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 offering in the specific SBG5 region. Here are some supplementary details : Start time : 01/11/2026 17: 55 UTC Impacted Service(s) : Some instances in the SBG5 region are temporarily unreachable. Customers Impact : Some customers are temporarily unable to access instances located in the specified region. Root Cause : A service disruption occurred due to an unexpected infrastructure malfunction. 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
4OVHcloud in the last 90 days
Full historyIncidents in 90 days
217
Days with an incident
90
Median duration
1 h 35 min
This incident
About the median
Other OVHcloud incidents
All incidentsOVHcloud·[SBG8][Virtual Private Servers] - VPS Incident Notification
Some Virtual Private Servers in the SBG8 region were temporarily unreachable. The incident affected some VPS in the SBG region. OVHcloud identified a network equipment issue as the cause. OVHcloud resolved the incident. The incident started at 17:55 UTC and ended at 19:54 UTC.
OVHcloud·[SBG6/8][Virtual Private Servers] - VPS Incident Notification
Some Virtual Private Servers in the SBG5, SBG6 and SBG8 regions were unreachable. OVHcloud reports that the incident is resolved. It lasted from 17:55 UTC to 19:30 UTC.
OVHcloud·[RBX3][Dedicated Servers] - Rack 46E19 Incident Notification
OVHcloud reports that servers in Rack 46E19, RBX3, were not accessible through the IPMI interface. The incident was caused by a network equipment issue. The incident is resolved and it lasted 2 hours and 23 minutes.
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.
OVHcloud·[ERI1][Network] - Rack ERI0102C03B Incident Notification
We had an incident on our Dedicated Servers offer which has now been resolved. Here are some supplementary details : Start time : 31/10/2026 14:36 UTC End time : 31/10/2026 14:57 UTC Impacted Service(s) : Public Network in Rack ERI0102C03B was temporarily unavailable. Customers Impact : Customers were temporarily unable to access their servers via Public Network in the specified rack. Root Cause : This incident was caused by a network equipment 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.cc/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.cc/feed.xml?providers=ovhcloud/feed subscribe https://outages.cc/feed.xml?providers=ovhcloudFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane