[SGP2][Infrastructure] - Rack SGP0202D03A maintenance notification
As part of our continuous improvement plan, we will be carrying out maintenance on our electrical infrastructure. Start time : 20/11/2026 02:30 UTC End time : 20/11/2026 06:30 UTC Service impact : In the worst case, customers could experience a temporary reboot or shutdown of their servers. Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our electrical 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 maintenance on our electrical infrastructure. Start time : 20/11/2026 02:30 UTC End time : 20/11/2026 06:30 UTC Service impact : In the worst case, customers could experience a temporary reboot or shutdown of their servers. Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our electrical infrastructure. Thank you for your understanding.
Affected components
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
257
Days with an incident
90
Median duration
1 h 40 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[RBX3][Dedicated Servers] - Rack 43N06 incident notification
OVHcloud reports that some Dedicated Servers in rack 43N06 in the RBX region were unavailable. OVHcloud identified an electrical equipment issue. OVHcloud resolved the incident, which lasted about 74 minutes.
OVHcloud·[GRA3][Dedicated Servers] - Rack GRA0326A03B incident notification
OVHcloud Dedicated Servers on rack GRA0326A03B in the GRA region had a partial outage. Some servers were temporarily unavailable. OVHcloud identified a cooling system issue. OVHcloud resolved the incident. The incident lasted about 2 hours and 24 minutes.
OVHcloud·[GLOBAL][Network] - API Network incident notification
OVHcloud reports that API requests on VPS services do not work correctly in the BHS, ERI, GRA, LIM, SBG, SGP, SYD, UK2, WAW, MIL, YNM, EU-WEST-LZ-MRS, US-EAST-LZ-ATL, US-EAST-LZ-DAL, US-EAST-LZ-MIA, US-EAST-LZ-NYC, US-EAST-VA, US-WEST-LZ-PAO, US-WEST-OR and EU-WEST-LZ-DLN regions. Customers can get slow responses or intermittent HTTP 500 errors. OVHcloud resolved the incident. It lasted 113 minutes.
OVHcloud·[EU/CA/MUM][Network] - API Network incident notification
OVHcloud API requests on the public cloud did not work in the BHS, DE, GRA, RBX, SBG, SGP, SYD, and UK regions. The US region was not affected. OVHcloud reports that the incident is resolved. It lasted 2 hours and 9 minutes.
OVHcloud·[DE2][Virtual Private Servers] - Some VPS incident notification
Some Virtual Private Servers did not work in the DE2 region. The affected components were LIM and Virtual Private Servers Global Infrastructure - LIM. OVHcloud reports that the incident is resolved. It lasted from 08:35 UTC to 10:23 UTC on 11 November 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