[BHS1/3/5][Public Cloud] - Compute Instance incident notification
OVHcloud reports that some Compute instances were unavailable in the BHS1, BHS3, and BHS5 regions. OVHcloud identified the cause and worked on a fix. The incident is resolved and lasted 33 minutes, from 06:34 UTC to 07:07 UTC.
State
Resolved
Started
Lasted
32 min
Worst impact
Partial outage
Timeline
3 updatesIdentified
32 min 100%
Updates
Times in UTCAs posted by OVHcloud
We would like to inform you that the incident affecting our Public Cloud offering has now been resolved. Please find the details of this incident below : Start time : 15/11/2026 06:34 UTC End time : 15/11/2026 07:07 UTC Impacted Service(s) : Some instances in the BHS1/3/5 regions were unavailable. Customers Impact : Customers were temporarily unable to access their instances located in the specified regions. 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 continuing to work on a fix for this issue.
We are currently experiencing an incident affecting our Public Cloud offering in the BHS5 region. The root cause has been identified. Please find the details of this incident below : Start time : 15/11/2026 06:34 UTC Impacted Service(s) : Some instances in the BHS5 region are unavailable. Customers Impact : Customers are temporarily unable to access their instances located in the specified region. Root Cause : A service disruption is occurring due to an unexpected underlying infrastructure malfunction. 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.
Affected components
6OVHcloud in the last 90 days
Full historyIncidents in 90 days
260
Days with an incident
90
Median duration
1 h 40 min
This incident
68% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[BHS][Virtual Private Servers] - VPS incident notification
Some Virtual Private Servers in the BHS region did not work. OVHcloud states that the incident is resolved. The incident lasted from 06:34 UTC to 07:07 UTC.
OVHcloud·[Global][DNS] - .TN DNS Hosting incident notification
The ns1.tn.ovh.net DNS server is temporarily unavailable. This affects the OVHcloud .TN DNS hosting service. Domains that use ns1.tn.ovh.net alone can have DNS resolution failures. OVHcloud reports that the incident is under investigation.
OVHcloud·[SGP1][Storage] - Block Storage incident notification
OVHcloud Block Storage volumes in the SGP1 region had degraded performance. OVHcloud reports that the incident is resolved. The incident lasted 58 minutes.
OVHcloud·[GRA][Web Hosting] - Cluster128 SSH/FTP services incident notification
We would like to inform you that an incident affected our Web Hosting offering on Cluster128. This incident has since been resolved. Please find the details of this incident below : Start time : 14/11/2026 08:18 UTC End time : 14/11/2026 09:30 UTC Impacted Service(s) : SSH and FTP services on Web Hosting Cluster128 were temporarily unavailable. Customers Impact : Customers were temporarily unable to access their files via SSH or FTP. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout
OVHcloud·[GRA1][Dedicated Servers] - Rack G127A24 incident notification
OVHcloud reports that the vRack network did not work for Dedicated Servers in rack G127A24 in the GRA region. The incident is resolved, and it lasted about 57 minutes. OVHcloud states that a network equipment issue caused the 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