[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":-5,"_6":7},"actionData","errors","root","routes/status-provider-incidents",{"_8":9,"_10":11,"_12":13},"provider",{"_35":53,"_20":54,"_22":55,"_56":57,"_58":59,"_60":61,"_62":63,"_64":65,"_17":-5,"_66":67,"_68":18,"_69":70},"history",{"_14":15,"_16":-5,"_17":18},"cursor","Y0Wbqv9DpOmo","incidents",[19],"nextCursor","sourceFetchedAt","2026-10-24T07:28:08.546Z",{"_20":21,"_22":23,"_24":25,"_26":27,"_28":29,"_30":-5,"_31":32,"_33":34,"_35":36,"_37":38},"name","[GLOBAL][Databases] - PostgreSQL 18 and PostGIS Compatibility Issue","status","MONITORING","impact","MINOR","startedAt","2026-03-30T12:36:18.000Z","updatedAt","2026-07-08T14:22:28.487Z","resolvedAt","officialUrl","https://stspg.io/hgbbpw5mr1nq","updates",[39,40,41,42],"id","KlMdxEY4xL21","isActive",true,{"_22":47,"_43":52,"_45":27},{"_22":47,"_43":50,"_45":51},{"_22":47,"_43":48,"_45":49},{"_22":23,"_43":44,"_45":46},"body","We have new information regarding the incident that affected your service(s).\n\nPlease find below an update on the situation:\nUpdate : 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.\nAs a reminder, this only affects customers using the PostGIS extension. PostgreSQL instances that do not use PostGIS are not impacted.\nIn 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.\nOngoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.\n\nWe will keep you updated on the progress and resolution.\n\nWe apologize for any inconvenience caused and appreciate your understanding.","occurredAt","2026-07-08T14:22:28.469Z","IDENTIFIED","We have new information regarding the incident that affected your service(s).\n\nPlease find below an update on the situation:\nUpdate : 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.\nAs a reminder, this only affects customers using the PostGIS extension. PostgreSQL instances that do not use PostGIS are not impacted.\nIn 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.\nOngoing Actions : We are closely monitoring the situation while the PostGIS team works on a resolution.\n\nWe will keep you updated on the progress and resolution.\n\nWe apologize for any inconvenience caused and appreciate your understanding.","2026-06-11T08:45:00.000Z","Our provider is still working on resolving the issue affecting our PostgreSQL offering.\nTo 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.\n\nFor any questions, please contact your usual point of contact or reach out to our support team.\n\nWe will keep you updated on the progress and resolution.","2026-04-09T14:08:25.674Z","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.\n\nHere are some supplementary details :\nStart time : 16/03/2026 08:00 UTC\nImpacted Service(s) : 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.\nAs a precaution, we strongly recommend postponing any upgrade to PostgreSQL version 18 and continuing to use PostgreSQL version 17, which remains compatible with PostGIS.\nRoot Cause : This incident is caused by PostGIS extension current version 3.5.\nOngoing Actions : The PostGIS team needs to fix this bug and release a new version of the extension (v3.6). In the meantime, our services remain fully functional without PostGIS.\n\nIf you have any questions, please contact your usual point of contact or reach out to our support team.\n\nWe will keep you updated on the progress and resolution.","8r1DXba8lk5m","OVHcloud - Public Cloud","MAINTENANCE","statusDescription","Service Under Maintenance","officialPageUrl","https://public-cloud.status-ovhcloud.com/","productDomain","ovhcloud.com","productDomainAliases",[],"scraperState","ENABLED","activeIncidentCount",1,"incidentSourceFetchedAt","slug","ovhcloud-public-cloud"]

OVHcloud - Public Cloud outage history

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