[GRA1][Network] - Room G107/G108A maintenance notification
As part of our continuous improvement plan, we will be carrying out maintenance on our network infrastructure. Start time : 17/11/2026 02:00 UTC End time : 17/11/2026 05:00 UTC List of concerned racks : - Rack G107A06 - Rack G107A07 - Rack G107A08 - Rack G107A09 - Rack G107A10 - Rack G107A11 - Rack G107A12 - Rack G107A13 - Rack G107B16 - Rack G107B18 - Rack G108A02 - Rack G108A03 - Rack G108A04 - Rack G108A05 - Rack G108A07 - Rack G108A08 - Rack G108A09 - Rack G108A10 Service impact : During the maintenance window, a network equipment serving the concerned racks will be replaced. Customers hosted in these racks may experience a temporary loss of network connectivity on their servers during the operation. Service improvement : As part of our continuous improvement policy, we will be replacing network equipment to ensure the reliability and resilience of our 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 network infrastructure. Start time : 17/11/2026 02:00 UTC End time : 17/11/2026 05:00 UTC List of concerned racks : - Rack G107A06 - Rack G107A07 - Rack G107A08 - Rack G107A09 - Rack G107A10 - Rack G107A11 - Rack G107A12 - Rack G107A13 - Rack G107B16 - Rack G107B18 - Rack G108A02 - Rack G108A03 - Rack G108A04 - Rack G108A05 - Rack G108A07 - Rack G108A08 - Rack G108A09 - Rack G108A10 Service impact : During the maintenance window, a network equipment serving the concerned racks will be replaced. Customers hosted in these racks may experience a temporary loss of network connectivity on their servers during the operation. Service improvement : As part of our continuous improvement policy, we will be replacing network equipment to ensure the reliability and resilience of our infrastructure. Thank you for your understanding.
As part of our continuous improvement plan, we will be carrying out maintenance on our network infrastructure. Start time : 17/11/2026 02:00 UTC End time : 17/11/2026 05:00 UTC List of concerned racks : - Rack G107A06 - Rack G107A07 - Rack G107A08 - Rack G107A09 - Rack G107A10 - Rack G107A11 - Rack G107A12 - Rack G107A13 - Rack G107B16 - Rack G107B18 - Rack G108A02 - Rack G108A03 - Rack G108A04 - Rack G108A05 - Rack G108A07 - Rack G108A08 - Rack G108A09 - Rack G108A10 Service impact : During the maintenance window, a network equipment serving the concerned racks will be replaced. Customers hosted in these racks may experience a temporary loss of network connectivity on their servers during the operation. Service improvement : As part of our continuous improvement policy, we will be replacing network equipment to ensure the reliability and resilience of our infrastructure. Thank you for your understanding.
Affected components
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
231
Days with an incident
90
Median duration
1 h 37 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[US/SYD][Infrastructure] - Backbone incident notification
We would like to inform you that an incident affected our Infrastructure offering. This incident has since been resolved. Please find the details of this incident below : Start time : 04/11/2026 13:37 UTC End time : 04/11/2026 14:00 UTC Impacted Service(s) : Increased latency was observed on the link between US and SYD. Customers Impact : Customers may have experienced increased latency when accessing their services passing from US and SYD. Root Cause : This incident was caused by our provider. We thank you for your understanding and patience throughout this incident.
OVHcloud·[DE1][Network] - Load Balancer incident notification
OVHcloud reports that the Network API in the DE1 region was unstable. Customers could not create or resize Load Balancers, and network administrative actions returned API errors. OVHcloud says the incident is resolved. It lasted about 11 hours.
OVHcloud·[GRA][Web Hosting] - Some Filerz incident notification
OVHcloud reports that some websites on some Filerz were temporarily unavailable in the GRA region. The affected components include clusters 100 to 128. OVHcloud reports that the incident is resolved. It started at 20:20 UTC and ended at 21:05 UTC, so it lasted 45 minutes.
OVHcloud·[GLOBAL][Dedicated Servers] - Administrative network task incident notification
OVHcloud reports that administrative changes to public and private network settings did not work on Dedicated Servers. The affected regions include BHS, CCH, ERI, GRA, IEB, LIM, MR9, RBX, SBG, SGP, SYD, WAW, YNM, YYZ, US-EAST-VA, US-WEST-OR and US-WEST-LZ-SEA. OVHcloud resolved the incident, which lasted about 13 hours and 18 minutes.
OVHcloud·[DE1][Network] - Load balancer incident notification
The load balancer delivery service in the DE1 region did not work. OVHcloud reports that the incident is resolved. The incident lasted from 17:00 UTC to 19:13 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