OVHcloud reported "[EU-WEST-PAR][Storage] - Object Storage S3 incident notification" on its status page at 2026-10-08 15:14 UTC.

When did the incident start and end?

It started at 2026-10-08 15:14 UTC and ended at 2026-10-15 09:37 UTC. It lasted 7 days.

How do I get alerts for OVHcloud?

Subscribe to the OVHcloud live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of OVHcloud. outages.live reads it every few minutes and keeps every update.

OVHcloudIncident · 2026-10-08 15:14 UTC

[EU-WEST-PAR][Storage] - Object Storage S3 incident notification

Q: What is affected?

OVHcloud lists these components: EU-WEST-PAR-A, EU-WEST-PAR-B, EU-WEST-PAR-C, Storage || Object storage - EU-WEST-PAR-A, Storage || Object storage - EU-WEST-PAR-B, Storage || Object storage - EU-WEST-PAR-C.

ResolvedOfficial update

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 updates

Oct 8Oct 10Oct 12Oct 13Oct 15

DegradedUpdate postedDates in UTC

Investigating

1 h 30 min 1%

Identified

1 h 32 min 1%

Monitoring

7 days 98%

Updates

Times in UTC

As posted by OVHcloud

Resolved2026-10-15 09:37 UTC

Monitoring2026-10-08 18:15 UTC

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.

Identified2026-10-08 16:43 UTC

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.

Investigating2026-10-08 15:14 UTC

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

EU-WEST-PAR-AEU-WEST-PAR-BEU-WEST-PAR-CStorage || Object storage - EU-WEST-PAR-AStorage || Object storage - EU-WEST-PAR-BStorage || Object storage - EU-WEST-PAR-C

OVHcloud in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

213

Days with an incident

Median duration

1 h 35 min

This incident

102× 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 7 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 7 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 7 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 7 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