Operational OVHcloud status
ovhcloud.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
No sign of a widespread OVHcloud problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: normal.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP AS16276 prefixes seen by 100% of RIPE RIS peers
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: BHS, DE, GRA
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 235 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: monitoring a fix on “[GLOBAL][Databases] - PostgreSQL 18 and PostGIS Compatibility Issue”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- AS16276 prefixes seen by 100% of RIPE RIS peers. evidence confidence: medium
What we don't know: what is happening inside OVHcloud's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “monitoring a fix”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: normal. Vendor status and outside signals roughly agree.
Who depends on whom
We don't map other services that depend on OVHcloud. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on OVHcloud, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers OVHcloud may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with OVHcloud. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
[GLOBAL][Databases] - PostgreSQL 18 and PostGIS Compatibility Issue
minor monitoring · started
4 updates
- identified
We are currently experiencing an ongoing incident and have determined origin of the issue to PostGIS plugin, affecting our PostgreSQL offer when using this specific plugin in version 3.5 and PG18. Here are some supplementary details : <b>Start time :</b> 16/03/2026 08:00 UTC <b>Impacted Service(s) :</b> Customers may experience issues when upgrading to PostgreSQL version 18, as the PostGIS extension is currently not functional on this version, potentially preventing the use of geospatial features. As a precaution, we strongly recommend postponing any upgrade to PostgreSQL version 18 and continuing to use PostgreSQL version 17, which remains compatible with PostGIS. <b>Root Cause :</b> This incident is caused by PostGIS extension current version 3.5. <b>Ongoing Actions :</b> The PostGIS team needs to fix this bug and release a new version of the extension (v3.6). In the meantime, our serv
- identified
Our provider is still working on resolving the issue affecting our PostgreSQL offering. To avoid issues with geospatial features, we still strongly recommend postponing any upgrade to PostgreSQL version 18 and continuing to use PostgreSQL version 17, which remains compatible with PostGIS. For any questions, please contact your usual point of contact or reach out to our support team. We will keep you updated on the progress and resolution.
- identified
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: <b>Update : </b> 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. <b>Ongoing Actions :</b> We are closely monitoring the situation while the PostGIS team works on a resolution. We will keep yo
- monitoring
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: <b>Update :</b> 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. <b>Ongoing Actions :</b> The incident has been identified and corrected. It is being closely monitored to ensure long-term stab
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.