[EU-WEST-PAR][Storage] - Object Storage incident notification
OVHcloud Object Storage S3 is slow for uploads and downloads in the EU-WEST-PAR region. This affects the EU-WEST-PAR-A, EU-WEST-PAR-B, and EU-WEST-PAR-C components. OVHcloud reports that the service is fully restored and monitoring continues.
State
Monitoring
Started
Ongoing for
1 h 23 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
1 h 8 min 82%
Monitoring
15 min 18%
Updates
Times in UTCAs posted by OVHcloud
We would like to inform you that our service has been fully restored as of 03/11/2026 09:53 UTC. Monitoring is still in place to ensure long-term stability. Please find the details of this incident below : Start time : 27/10/2026 20:00 UTC Impacted Service(s) : Object Storage S3 experienced increased response times in the specified region. Customers Impact : Customers may have experienced slowness when uploading or retrieving their data located in the specified region. We apologize for any inconvenience caused and appreciate your understanding.
We are currently experiencing an incident affecting our Object Storage offering, which is causing temporary latency issues in the EU-WEST-PAR region. Please find the details of this incident below : Start time : 27/10/2026 20:00 UTC Impacted Service(s) : Object Storage S3 is experiencing increased response times in the specified region. Customers Impact : Customers may experience slowness when uploading or retrieving their data located in the specified region. Ongoing Actions : Our teams are investigating to determine the origin of the incident to 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
225
Days with an incident
90
Median duration
1 h 37 min
This incident
About the median
Other OVHcloud incidents
All incidentsOVHcloud·[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.
OVHcloud·[DE1][Network] - Network API incident notification
OVHcloud reports that the Network API for the public network and the private network (vRack) is unstable in the DE1 region. Customers can get API errors when they create, change, or manage public and private network (vRack) configurations in DE1. OVHcloud is investigating the cause.
OVHcloud·[Global][AI & Machine Learning] - AI Notebooks, AI Training, AI Deploy incident notification
We would like to inform you that an incident affected our AI & Machine Learning offering. This incident has since been resolved. Please find the details of this incident below : Start time : 31/10/2026 07:08 UTC End time : 31/10/2026 07:58 UTC Impacted Service(s) : AI Notebooks, AI Training and AI Deploy services were temporarily unavailable. Customers Impact : Customers were temporarily unable to create, manage or access their notebooks, training jobs and AI applications. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.
OVHcloud·[BHS5][Dedicated Servers] - Racks T05B28, T05B29 incident notification
Some Dedicated Servers in racks T05B28 and T05B29 in BHS5 were unavailable. OVHcloud reports that the incident is resolved. The incident lasted about 1 hour.
OVHcloud·[RBX8][Dedicated Servers] - Rack R809R19 Incident Notification
OVHcloud Dedicated Servers in Rack R809R19 at RBX were temporarily unavailable. OVHcloud reports that the incident is resolved. The incident lasted from 03:33 UTC to 04:49 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