[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.
State
Resolved
Started
Lasted
27 min
Worst impact
Partial outage
Timeline
5 updatesInvestigating
11 min 41%
Identified
16 min 59%
Updates
Times in UTCAs posted by OVHcloud
We are pleased to inform you that the incident affecting our Web Hosting offering has been resolved. Start time : 03/11/2026 20:20 UTC End time : 03/11/2026 21:05 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Web Hosting offer. Here are some supplementary details : Start time : 03/11/2026 20:20 UTC Impacted Service(s) : Some Websites on some Filerz are temporarily unavailable. Customers Impact : Some customers may be temporarily unable to access their websites through some Filerz. Root Cause : This incident is caused by a software issue. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Web Hosting offer. Here are some supplementary details : Start time : 03/11/2026 20:20 UTC Impacted Service(s) : Some Website on some Filerz are temporarily unavailable. Customers Impact : Some customers may be temporarily unable to access their websites through some Filerz. Root Cause : This incident is caused by a software issue. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Web Hosting offer. Here are some supplementary details : Start time : 03/11/2026 20:20 UTC Impacted Service(s) : Some Filerz are temporarily unavailable. Customers Impact : Some customers may be temporarily unable to access their websites through some Filerz. Root Cause : This incident is caused by a software issue. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
We are currently experiencing an event affecting our Web Hosting offer. Start time : 03/11/2026 20:20 UTC Our teams are fully committed to investigating this issue and working towards a resolution as soon as possible. As investigations are ongoing, we will share any new findings or updates with you as soon as possible. We apologize for any inconvenience caused and appreciate your understanding.
Affected components
46OVHcloud in the last 90 days
Full historyIncidents in 90 days
229
Days with an incident
90
Median duration
1 h 36 min
This incident
72% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[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.
OVHcloud·[GRA11][Network] - Network API incident notification
OVHcloud reports that the Network API for the public network and the private network (vRack) was unstable in the GRA11 region. The Managed Kubernetes Service in GRA11 was also affected. OVHcloud says that the incident is resolved and that it lasted about 6 hours and 18 minutes.
OVHcloud·[Global][Dedicated Servers] - Delivery incident notification
OVHcloud Dedicated Servers delivery was degraded. The processing of suspension and reactivation requests was delayed in Zone Europe, Zone APAC, and Zone Canada. OVHcloud reports that the incident is resolved. It lasted about 7 hours and 25 minutes.
OVHcloud·[RBX][Storage and Backups] - NAS HA Cluster11003 incident notification
We would like to inform you that an incident affected our NAS HA offering on the Cluster11003 in the RBX region. This incident has since been resolved. Please find the details of this incident below : Start time : 03/11/2026 10:10 UTC End time : 03/11/2026 10:24 UTC Impacted Service(s) : Some NAS HA services on the Cluster11003 were temporarily unavailable. Customers Impact : Customers were temporarily unable to access their data located on the Cluster11003. Root Cause : This incident was caused by a hardware issue. We thank you for your understanding and patience throughout this incident.
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