OVHcloud has one open incident. Our tests are getting responses. No recent reports.
PostgreSQL 18 with PostGIS: compatibility issue under monitoring. A defect in the newest PostGIS (geographic extension) version may corrupt geospatial data, so OVHcloud has not enabled PostGIS support on PostgreSQL 18. Instances without PostGIS are not affected.
Is it just me?
We test OVHcloud from your connection and compare it with our servers.
We do not store your IP, only an anonymous fingerprint that changes daily, to count each person once.
Official statusDegraded
All Systems Operational
Our tests77 ms
We contact the service every 5 minutes from Ireland (EU).
User reports0 in 30 min
Use the "It is failing for me too" button to warn others.
What is going on, explained
May affect Portugal
What is happening
A defect in the newest PostGIS (geographic extension) version may corrupt geospatial data, so OVHcloud has not enabled PostGIS support on PostgreSQL 18. Instances without PostGIS are not affected.
Who is affected
Only customers who use the PostGIS extension with PostgreSQL 18. The company lists components in several regions, including EU-WEST-PAR (Paris), so Europe is included, but there is no confirmation that the problem specifically affects Portugal.
What OVHcloud is doing
The company says the incident has been identified and corrected and is being monitored to ensure long-term stability. It is waiting for a fixed PostGIS release before allowing PostGIS on PostgreSQL 18.
What to do meanwhile
If you use PostGIS, stay on PostgreSQL 17, which is fully compatible, and postpone any upgrade to version 18 until a fixed PostGIS release is available. If you do not use PostGIS, you do not need to do anything.
Written by SignalOkay's AI from official sources, .
What OVHcloud published
[GLOBAL][Databases] - PostgreSQL 18 and PostGIS Compatibility IssueMonitoring
Started (228 days)
Latest update
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 appreciate your understanding.
Affects: BHS, DE, GRA, EU-SOUTH-MIL, AP-SOUTH-MUM, EU-WEST-PAR, RBX, SBG, SGP, UK, US-EAST-VA, US-WEST-ORSee the original message
Response time in the last 24 hours
We are collecting data. The chart appears after the first hour.
Measured by our tests from Ireland. Red marks periods without a response.