OVHcloud is having issues

Open at OVHcloud

• [EU-WEST-PAR][Storage] - Object Storage S3 incident notificationmonitoring · impact minor

  Since 2026-10-08 15:14 UTC · EU-WEST-PAR-A, EU-WEST-PAR-B, EU-WEST-PAR-C

  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 incon…

• [GLOBAL][Databases] - PostgreSQL 18 and PostGIS Compatibility Issuemonitoring · impact minor

  Since 2026-03-30 12:36 UTC · BHS, DE, GRA, EU-SOUTH-MIL, AP-SOUTH-MUM, EU-WEST-PAR +6

  We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : PostGIS support for PostgreSQL 18 was introduced in a newer PostGIS version. However, an identified defect carries a risk of data corruption for geospatial data, so we have chosen not to enable it on our offer yet. We are waiting for a PostGIS release that fixes this issue before allowing PostGIS to be used on PostgreSQL 18. As a reminder, this only affects custom…

Text written by OVHcloud, shown unchanged.

OVHcloud incidents, last 90 days

Incidents

15

7 major or critical

Typical time to resolve

49 min

median

Nine in ten within

4 days

major ones: 1 h 29 min

Longest

41 days

record since 2026-08-26

Questions

Is OVHcloud down right now?

Partly. As of 2026-10-10 07:16 UTC, OVHcloud is having issues, with an open incident: "[EU-WEST-PAR][Storage] - Object Storage S3 incident notification". This page reads the status again every 3 minutes.

How long do OVHcloud outages usually last?

Of the 15 incidents OVHcloud reported in the last 90 days, half were resolved within 49 min and nine in ten within 4 days; the longest took 41 days. Incidents rated major or critical typically took 1 h 29 min. These are the provider's own start and end times.

Where does this status come from?

From OVHcloud's own status page API at https://public-cloud.status-ovhcloud.com. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are OVHcloud's words.

Can I get an alert when OVHcloud goes down?

Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when OVHcloud reports an incident and one when it is over. There is also an RSS feed at https://upbutler.com/status/ovh/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.

How can my agent or app check OVHcloud status?

Fetch https://upbutler.com/status/ovh/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"ovh"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or OVHcloud's?

Add "ovh" to the dependencies of your UpButler workspace. When one of your monitors fails while OVHcloud has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Also check

• Amazon Web Services
• Google Cloud
• Microsoft Azure
• Cloudflare
• DigitalOcean
• Hetzner
• Fastly
• bunny.net
• All cloud and edge
• All services