[WAW1][Cooling System] - Rack WAW0106A03C
As part of our continuous improvement plan, we will be carrying out a maintenance on our cooling infrastructure. Start time: 23/11/2026 07:00 UTC End time: 23/11/2026 15:00 UTC Service impact: During this maintenance, the cooling system's efficiency may be temporarily reduced for some servers, potentially lowering performance. Despite ongoing mitigation efforts, customers could still experience a temporary reboot or shutdown in the worst case. Service improvement: As part of our continuous improvement policy, we will be doing a maintenance on our cooling infrastructure. Thank you for your understanding.
The latest update from OVHcloud.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by OVHcloud
As part of our continuous improvement plan, we will be carrying out a maintenance on our cooling infrastructure. Start time: 23/11/2026 07:00 UTC End time: 23/11/2026 15:00 UTC Service impact: During this maintenance, the cooling system's efficiency may be temporarily reduced for some servers, potentially lowering performance. Despite ongoing mitigation efforts, customers could still experience a temporary reboot or shutdown in the worst case. Service improvement: As part of our continuous improvement policy, we will be doing a maintenance on our cooling infrastructure. Thank you for your understanding.
Affected components
1OVHcloud in the last 90 days
Full historyIncidents in 90 days
262
Days with an incident
90
Median duration
1 h 41 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[SBG3][Managed VMware vSphere] - Racks S345A01, S345A02 incident notification
OVHcloud reports that some hosts in racks S345A01 and S345A02 in SBG3 are temporarily unavailable. This affects the Managed VMware vSphere service and Compute in the SBG region. OVHcloud has identified the incident and teams are working to restore service.
OVHcloud·[SBG3][Dedicated Servers] - Rack S345A03 incident notification
Some Dedicated Servers in rack S345A03 in the SBG region are temporarily unavailable. OVHcloud reports that the root cause is identified and that teams work to restore service. OVHcloud states the cause is a cooling system issue.
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.
OVHcloud·[US-EAST-VA][Storage] - Object Storage Incident Notification
OVHcloud Object Storage in the US-EAST-VA region had a partial outage. High Performance and Standard Object Storage had increased latency and 500/503 errors. OVHcloud reports that the incident is resolved. The incident lasted 1 hour and 43 minutes.
OVHcloud·[RBX8][Dedicated Servers] - Racks RBX0841A05A and RBX0841A05B incident notification
OVHcloud Dedicated Servers in racks RBX0841A05A and RBX0841A05B were temporarily unavailable in the RBX region. OVHcloud reports that the incident is resolved. The incident lasted from 13:09 UTC to 18:36 UTC on 12/11/2026.
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