[RBX4][Dedicated Servers] - Rack 54B16 maintenance notification
As part of our continuous improvement plan, maintenance is scheduled on our Bare Metal offer, affecting servers in rack 54B16. Start time : 22/11/2026 03:00 UTC End time : 22/11/2026 03:30 UTC Service impact : vRack network will be temporarily unavailable during the maintenance for servers in 54B16. Service improvement : Following our continuous improvement policy of our network infrastructure, we will be doing a maintenance on a network equipment. 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, maintenance is scheduled on our Bare Metal offer, affecting servers in rack 54B16. Start time : 22/11/2026 03:00 UTC End time : 22/11/2026 03:30 UTC Service impact : vRack network will be temporarily unavailable during the maintenance for servers in 54B16. Service improvement : Following our continuous improvement policy of our network infrastructure, we will be doing a maintenance on a network equipment. Thank you for your understanding.
Affected components
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
260
Days with an incident
90
Median duration
1 h 42 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[BHS5][Dedicated Servers] - Rack T05G37 incident notification
Some Dedicated Servers in rack T05G37 in the BHS region are temporarily unavailable. Customers cannot access servers on that rack. OVHcloud identified the cause as a cooling system issue and reports that the fix is in progress.
OVHcloud·[GRA3][Dedicated Servers] - Rack GRA0325B05A incident notification
OVHcloud reports that the vRack network does not work in rack GRA0325B05A in the GRA region. This affects Dedicated Servers in that rack. OVHcloud identified the cause as a cooling system issue. OVHcloud teams work to restore service.
OVHcloud·[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.
OVHcloud·[Global][Collaborative Solutions] - Zimbra incident notification
OVHcloud reports that some Zimbra mailboxes were temporarily unavailable in the Collaborative Solutions offering. Web Access, Delivery email, and Operations were affected. OVHcloud states that the incident is resolved. It lasted from 13 November 2026 23:32 UTC to 14 November 2026 02:52 UTC.
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.
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