[GRA][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 : 03/10/2026 02:00 UTC End time : 03/10/2026 at 04:27 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
The latest update from OVHcloud.
State
Resolved
Started
30 d ago
2026-10-03 03:06 UTC
Lasted
2 days
until 2026-10-05 11:47 UTC
Worst impact
Partial outage
Timeline
3 updatesIdentified
1 h 41 min 3%
Monitoring
2 days 97%
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 : 03/10/2026 02:00 UTC End time : 03/10/2026 at 04:27 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
We would like to inform you that our service has been fully restored as of 03/10/2026 at 04:27 UTC. Monitoring is still in place to ensure long-term stability. Please find the details of this incident below : Start time : 03/10/2026 02:00 UTC Impacted Service(s) : Object Storage S3 service was disrupted in the GRA region. Customers Impact : Customers may have experienced 500/503 errors when handling their objects. These errors mainly affected deletion requests. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. 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 region. Here are some supplementary details : Start time : 03/10/2026 02:00 UTC Impacted Service(s) : Object Storage S3 (standard and highperf) service is disrupted in the GRA region. Customers Impact : Customers may experience issues downloading or uploading their objects due to 500/503 errors. These errors mainly affect deletion requests. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. 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.
Affected components
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
217
Days with an incident
90
Median duration
1 h 35 min
This incident
36× 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
OVHcloud reports that servers in Rack 46E19, RBX3, were not accessible through the IPMI interface. The incident was caused by a network equipment issue. The incident is resolved and it lasted 2 hours and 23 minutes.
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