[WAW1][Dedicated Servers] - Rack W17A02 incident notification
OVHcloud reports that all Dedicated Servers in rack W17A02 in the WAW1 region were temporarily unavailable. OVHcloud reports that a cooling system issue caused the outage. The incident is resolved and lasted 5 minutes.
State
Resolved
Started
Lasted
6 min
Worst impact
Partial outage
Timeline
2 updatesInvestigating
6 min 100%
Updates
Times in UTCAs posted by OVHcloud
We would like to inform you that the incident affecting our Dedicated Servers offering has now been resolved. Please find the details of this incident below : Start time : 14/11/2026 00:20 UTC End time : 14/11/2026 00:25 UTC Impacted Service(s) : All servers in the rack W17A02 were temporarily unavailable. Customers Impact : Customers were temporarily unable to access their servers located on the specified rack. Root Cause : This incident was caused by a cooling system issue. We thank you for your understanding and patience throughout this incident.
We are currently experiencing an incident affecting our Dedicated Servers offering, which is causing temporary availability issues in the rack W17A02 in WAW1. Please find the details of this incident below : Start time : 14/11/2026 00:20 UTC Impacted Service(s) : All servers in the rack W17A02 are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their servers located on the specified rack. 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
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
265
Days with an incident
90
Median duration
1 h 40 min
This incident
94% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[Global][Collaborative Solutions] - Zimbra incident notification
Some Zimbra mailboxes in the Collaborative Solutions service are temporarily unavailable. Web Access, Delivery email, and Operations are affected. OVHcloud reports that it is investigating the incident.
OVHcloud·[GRA4][Web Hosting] - Databases incident notification
OVHcloud reports that SharedSQL databases on sharedsql052.eu012 in GRA4 were unreachable. The incident is resolved. It lasted 28 minutes, from 21:26 UTC to 21:54 UTC.
OVHcloud·[SBG3][Managed VMware vSphere] - Racks S345A01, S345A02 incident notification
OVHcloud reports that some hosts in racks S345A01 and S345A02 in SBG3 are unavailable. The Managed VMware vSphere service in SBG - Compute has a partial outage. OVHcloud states that service was fully restored at 22:04 UTC and monitoring continues.
OVHcloud·[SBG3][Dedicated Servers] - Rack S345A03 incident notification
Some servers in rack S345A03 in the SBG region are unavailable. This affects the OVHcloud Dedicated Servers offering. OVHcloud reports that the cause is identified. A significant number of servers work again, and OVHcloud teams continue to restore service.
OVHcloud·[SYD][Dedicated Servers] - Room S2-5X incident notification
The public network did not work for OVHcloud Dedicated Servers in several racks of the SYD zone. OVHcloud reported a network equipment issue. OVHcloud resolved the incident after 53 minutes.
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