Live

[GRA][Web Hosting] - Multiple Filerz incident notification

We are pleased to inform you that the incident affecting our Web Hosting offering has been resolved. Start time : 28/10/2026 09:45 UTC End time : 29/10/2026 15:19 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.

The latest update from OVHcloud.

State

Resolved

Started

5 d ago

2026-10-28 10:05 UTC

Lasted

29 h 20 min

until 2026-10-29 15:25 UTC

Worst impact

Degraded

Timeline

6 updates
10:0517:2500:4508:0515:25
DegradedUpdate postedTimes in UTC

Investigating

9 h 6 min 31%

Identified

20 h 14 min 69%

Updates

Times in UTC

As posted by OVHcloud

Resolved2026-10-29 15:25 UTC

We are pleased to inform you that the incident affecting our Web Hosting offering has been resolved. Start time : 28/10/2026 09:45 UTC End time : 29/10/2026 15:19 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.

Identified2026-10-28 19:35 UTC

We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Between 28/10/2026 17:30 UTC and 28/10/2026 18:00 UTC, some websites hosted on the affected Filerz were temporarily unavailable. Access has since been restored, and customers may now only experience latency on their websites. List of the affected filerz: - filez1628 cluster131 - filerz2186 cluster100 - filerz1046 cluster129 - filerz1812 cluster131 - filerz152 cluster126 - filerz167 cluster126 - filerz66 cluster120 - filerz344 cluster105 - filerz649 cluster110 - filerz545 cluster111 - filerz140 cluster126 - filerz981 cluster128 Ongoing Actions : The root cause 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.

Identified2026-10-28 19:11 UTC

We are currently experiencing an incident affecting our Web Hosting offering, which is causing temporary latency issues on multiple Filerz. The root cause has been identified. Please find the details of this incident below : Start time : 28/10/2026 09:45 UTC Impacted Service(s) : The following Filerz are experiencing latency issues : - filez1628 cluster131 - filerz2186 cluster100 - filerz1046 cluster129 - filerz1812 cluster131 - filerz152 cluster126 - filerz167 cluster126 - filerz66 cluster120 - filerz344 cluster105 - filerz649 cluster110 - filerz545 cluster111 - filerz140 cluster126 - filerz981 cluster128 Customers Impact : Customers are temporarily experiencing latency on their websites hosted on the affected Filerz. Root Cause : This incident is caused by a software issue. Ongoing Actions : Our teams are actively working 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 un

Investigating2026-10-28 17:59 UTC

We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Further investigation has shown that the incident impacts additional filerz. The full list of affected filerz is now as follows: - filez1628 cluster131 - filerz2186 cluster100 - filerz1046 cluster129 - filerz1812 cluster131 - filerz152 cluster126 - filerz167 cluster126 - filerz66 cluster120 - filerz344 cluster105 - filerz649 cluster110 - filerz545 cluster111 - filerz140 cluster126 - filerz981 cluster128 Ongoing Actions : Our teams remain fully mobilised and are working to restore service as quickly as possible. Further analysis is in progress to confirm the origin of the incident. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

Investigating2026-10-28 16:34 UTC

We are following up on the incident affecting your service(s). Please find below an update on the situation: Update : The investigation to determine the root cause of the incident is still ongoing. Ongoing Actions : Our teams remain fully mobilised and are working to restore service as quickly as possible. Further analysis is in progress to confirm the origin of the incident. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

Investigating2026-10-28 10:05 UTC

We are currently investigating an incident affecting our Web Hosting offering, which is causing temporary latency issue in multiple Filerz. Here are some supplementary details : Start time : 28/10/2026 09:45 UTC Impacted Service(s) : The following Filerz list is experiencing slowness : - filerz344 cluster105 - filerz649 cluster110 - filerz545 cluster111 - filerz140 cluster126 - filerz981 cluster128 Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

Affected components

18
Cluster100Cluster105Cluster110Cluster111Cluster120Cluster126Cluster128Cluster129

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

213

Days with an incident

90

Median duration

1 h 35 min

This incident

19× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

41 days
median 1 h 35 min
90 days agoToday

Other OVHcloud incidents

All incidents

OVHcloud·[SBG8][Virtual Private Servers] - VPS Incident Notification

OVHcloud reports that some Virtual Private Servers in the SBG8 region were temporarily unreachable. OVHcloud identified the cause as a network equipment issue. The incident is resolved and lasted about 1 hour and 59 minutes.

Resolvedresolved 6 h ago

OVHcloud·[SBG6/8][Virtual Private Servers] - VPS Incident Notification

We are pleased to inform you that the incident affecting our VPS offering has been resolved. Start time : 01/11/2026 17:55 UTC End time : 01/11/2026 19:30 UTC Root Cause : This incident was caused by a network equipment issue. We apologize for any inconvenience caused and appreciate your understanding.

Resolvedresolved 6 h ago

OVHcloud·[RBX3][Dedicated Servers] - Rack 46E19 Incident Notification

We are pleased to inform you that the incident affecting our Dedicated Servers offering has been resolved. Start time : 01/11/2026 17:15 UTC End time : 01/11/2026 19:38 UTC Root Cause : This incident was caused by a network equipment issue. We apologize for any inconvenience caused and appreciate your understanding.

Resolvedresolved 6 h ago

OVHcloud·[SBG5/7][Compute - Instance] - Compute Instance Incident Notification

We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 01/11/2026 17:55 UTC End time : 01/11/2026 19:30 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

Resolvedresolved 6 h ago

OVHcloud·[RBX2][Dedicated Servers] - Rack 21D12 Incident Notification

We are pleased to inform you that the incident affecting our Dedicated Servers offering has been resolved. Start time : 31/10/2026 19:38 UTC End time : 31/10/2026 22:10 UTC Root Cause : This incident was caused by an electrical equipment issue. We apologize for any inconvenience caused and appreciate your understanding.

Resolvedresolved 1 d ago

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=ovhcloud
Slack
/feed subscribe https://outages.live/feed.xml?providers=ovhcloud

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane