[AP-SOUTH-MUM-1][Storage] - S3 Object Storage incident notification
We are pleased to inform you that the incident affecting our Object Storage offering in AP-SOUTH-MUM-1 region has been resolved. Start time : 15/10/2026 11:30 UTC End time : 15/10/2026 15:05 UTC Root Cause : This incident was caused by another incident : https://network.status-ovhcloud.com/incidents/h9zynmg40bbz We apologize for any inconvenience caused and appreciate your understanding.
The latest update from OVHcloud.
State
Resolved
Started
18 d ago
2026-10-15 12:24 UTC
Lasted
19 h 57 min
until 2026-10-16 08:21 UTC
Worst impact
Partial outage
Timeline
3 updatesMonitoring
3 h 4 min 15%
Identified
16 h 53 min 85%
Updates
Times in UTCAs posted by OVHcloud
We are pleased to inform you that the incident affecting our Object Storage offering in AP-SOUTH-MUM-1 region has been resolved. Start time : 15/10/2026 11:30 UTC End time : 15/10/2026 15:05 UTC Root Cause : This incident was caused by another incident : https://network.status-ovhcloud.com/incidents/h9zynmg40bbz We apologize for any inconvenience caused and appreciate your understanding.
We are currently experiencing an incident affecting our Object Storage offering in the AP-SOUTH-MUM-1 region. The root cause has been identified. Please find the details of this incident below : Start time : 15/10/2026 11:30 UTC Impacted Service(s) : S3 Object Storage is experiencing disconnections and 503 errors in the AP-SOUTH-MUM-1 region. Customers Impact : Customers may experience disconnections and 503 errors when accessing, uploading or retrieving their objects stored in the specified region. Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/h9zynmg40bbz 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 understanding.
Service has been fully restored since 15/10/2026 11:35 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 15/10/2026 11:30 UTC Impacted Service(s) : Disconnection and 503 errors observed on S3 Object Storage. Customers Impact : Customers were temporarily facing disconnection and 503 errors when trying to access and use their objects located in AP-SOUTH-MUM-1. Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/h9zynmg40bbz We apologize for any inconvenience caused and appreciate your understanding.
Affected components
2Follow 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