[EU-WEST-PAR][Storage] - Object Storage S3 incident notification
We are pleased to inform you that the incident affecting our Object Storage S3 offering has been resolved. Start time : 08/10/2026 00:00 UTC End time : 08/10/2026 18:14 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
24 d ago
2026-10-08 15:14 UTC
Lasted
7 days
until 2026-10-15 09:37 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
1 h 30 min 1%
Identified
1 h 32 min 1%
Monitoring
7 days 98%
Updates
Times in UTCAs posted by OVHcloud
We are pleased to inform you that the incident affecting our Object Storage S3 offering has been resolved. Start time : 08/10/2026 00:00 UTC End time : 08/10/2026 18:14 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
Service has been fully restored since 08/10/2026 18:14 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 08/10/2026 00:00 UTC Impacted Service(s) : Latency was observed for Object Storage S3 in the specified region. Customers Impact : Customers were temporarily facing latency when trying to access and use their objects located in EU-WEST-PAR region. Root Cause : This incident is 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 Object Storage S3 offer on the specific EU-WEST-PAR region. Here are some supplementary details : Start time : 08/10/2026 00:00 UTC Impacted Service(s) : Latency observed for Object Storage S3 in the specified region. Customers Impact : Customers may still experience some latency when accessing and using their objects located in EU-WEST-PAR region, though it has significantly decreased. Root Cause : This incident is caused by a software issue. Ongoing Actions : The incident has been identified and a significant reduction in latency has been observed. Our teams remain mobilised to fully 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 investigating an incident affecting our Object Storage S3 offering, which is causing temporary latency issue in the EU-WEST-PAR region. Here are some supplementary details : Start time : 08/10/2026 00:00 UTC Impacted Service(s) : Latency observed for Object Storage S3 in the specified region. Customers Impact : Customers are temporarily facing latency when trying to access and use their objects located in EU-WEST-PAR region. 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
6OVHcloud in the last 90 days
Full historyIncidents in 90 days
217
Days with an incident
90
Median duration
1 h 35 min
This incident
102× the median
Other OVHcloud incidents
All incidentsOVHcloud·[SBG8][Virtual Private Servers] - VPS Incident Notification
Some Virtual Private Servers in the OVHcloud SBG8 region are temporarily unreachable. OVHcloud has identified the incident and states that a network equipment issue causes it. OVHcloud teams are working to restore service.
OVHcloud·[SBG6/8][Virtual Private Servers] - VPS Incident Notification
Some Virtual Private Servers in the SBG5, SBG6 and SBG8 regions were unreachable. OVHcloud reports that the incident is resolved. It lasted from 17:55 UTC to 19:30 UTC.
OVHcloud·[RBX3][Dedicated Servers] - Rack 46E19 Incident Notification
Servers in Rack 46E19 in the RBX region are not accessible through the IPMI interface. The Dedicated Servers network in RBX is affected. OVHcloud reports that the incident is identified. The cause is a network equipment issue, and teams work to restore service.
OVHcloud·[SBG5/7][Compute - Instance] - Compute Instance Incident Notification
OVHcloud Compute Instance service did not work for some instances in the SBG5 and SBG7 regions. OVHcloud reports that the incident is resolved. The incident lasted from 17:55 UTC to 19:30 UTC.
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.
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.cc/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.cc/feed.xml?providers=ovhcloud/feed subscribe https://outages.cc/feed.xml?providers=ovhcloudFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane