OVHcloud lists these components: BHS, DE, GRA, EU-SOUTH-MIL, AP-SOUTH-MUM, EU-WEST-PAR, and 20 more.

When did the incident start and end?

It started at 2026-03-30 12:36 UTC. This page shows the end time when OVHcloud marks it resolved.

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. A language model writes the summary from those updates.

OVHcloudIncident · 2026-03-30 12:36 UTC

[GLOBAL][Databases] - PostgreSQL 18 and PostGIS Compatibility Issue

Q: What happened?

OVHcloud reported "[GLOBAL][Databases] - PostgreSQL 18 and PostGIS Compatibility Issue" on its status page at 2026-03-30 12:36 UTC. PostGIS does not work with PostgreSQL 18 on OVHcloud Databases in the BHS, DE, GRA, EU-SOUTH-MIL, AP-SOUTH-MUM, EU-WEST-PAR, RBX, SBG, SGP, UK, US-EAST-VA, US-WEST-OR, and WAW regions. OVHcloud reports the incident as monitored. PostgreSQL instances without PostGIS are not affected.

DegradedOfficial update

PostGIS does not work with PostgreSQL 18 on OVHcloud Databases in the BHS, DE, GRA, EU-SOUTH-MIL, AP-SOUTH-MUM, EU-WEST-PAR, RBX, SBG, SGP, UK, US-EAST-VA, US-WEST-OR, and WAW regions. OVHcloud reports the incident as monitored. PostgreSQL instances without PostGIS are not affected.

State

Monitoring

Started

216 d ago

2026-03-30 12:36 UTC

Ongoing for

216 days

Worst impact

Degraded

Timeline

1 update

Mar 30May 23Jul 16Sep 8Nov 1

DegradedUpdate postedDates in UTC

Monitoring

216 days 100%

Updates

Times in UTC

As posted by OVHcloud

Monitoring2026-11-01 17:39 UTC

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 customers using the PostGIS extension. PostgreSQL instances that do not use PostGIS are not impacted. In the meantime, we still strongly recommend that PostGIS users postpone any upgrade to PostgreSQL 18 and remain on PostgreSQL 17, which is fully compatible with PostGIS. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appr

Affected components

BHSDEGRAEU-SOUTH-MILAP-SOUTH-MUMEU-WEST-PARRBXSBG

OVHcloud in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

217

Days with an incident

Median duration

1 h 35 min

This incident

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

Some Virtual Private Servers in the SBG8 region were temporarily unreachable. The incident affected some VPS in the SBG region. OVHcloud identified a network equipment issue as the cause. OVHcloud resolved the incident. The incident started at 17:55 UTC and ended at 19:54 UTC.

Resolvedresolved 2 h ago

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.

Resolvedresolved 2 h ago

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.

Resolvedresolved 2 h ago

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.

Resolvedresolved 3 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.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.

RSS

https://outages.cc/feed.xml?providers=ovhcloud

Slack

/feed subscribe https://outages.cc/feed.xml?providers=ovhcloud

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane