[SBG3][Infrastructure] - High-voltage electrical maintenance notification
As part of our continuous improvement plan, we will be carrying out maintenance on our high-voltage electrical infrastructure, in coordination with our provider. Start time : 23/11/2026 07:00 UTC End time : 23/11/2026 16:00 UTC Service impact : No service impact is expected during the maintenance window. Our teams will closely monitor the maintenance activities to ensure service continuity. Service improvement : As part of our continuous improvement policy, we are performing preventive maintenance on our electrical infrastructure to ensure its continued reliability and resilience. 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 maintenance on our high-voltage electrical infrastructure, in coordination with our provider. Start time : 23/11/2026 07:00 UTC End time : 23/11/2026 16:00 UTC Service impact : No service impact is expected during the maintenance window. Our teams will closely monitor the maintenance activities to ensure service continuity. Service improvement : As part of our continuous improvement policy, we are performing preventive maintenance on our electrical infrastructure to ensure its continued reliability and resilience. 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 41 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[SYD][Dedicated Servers] - Room S2-5X incident notification
The public network does not work for Dedicated Servers in several racks of the SYD zone. OVHcloud reports that it identified the state of the incident. The cause is a network equipment issue.
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.
OVHcloud·[GRA3][Dedicated Servers] - Rack GRA0326A03B incident notification
OVHcloud reports that the public network did not work in rack GRA0326A03B in the GRA region. This affected Dedicated Servers. The incident is resolved. It lasted from 10:37 UTC to 14:35 UTC.
OVHcloud·[RBX/GRA/SBG][Collaborative Solutions] - EmailPro, Hosted Exchange, Private Exchange, MX Plan incident notification
OVHcloud reports that some management operations, such as password changes and account deletions, did not work on EmailPro, Hosted Exchange, Private Exchange and MX Plan in the RBX, GRA and SBG datacenters. OVHcloud says the incident is resolved. It lasted 1 hour and 41 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