Public Cloud Status

Resolved: We are pleased to inform you that the incident affecting our Public Cloud Network API offer in GRA9 region has been resolved.

Start time : 08/04/2026 09:06 UTC End time : 08/04/2026 10:12 UTC Root Cause : This incident was caused by a software issue.

We apologize for any inconvenience caused and appreciate your understanding.

Investigating: We are currently investigating an incident affecting our Network offering, which is causing temporary availability issue in the Public Cloud Network API.

Here are some supplementary details :

Start time : 08/04/2026 09:06 UTC Impacted Service(s) : The API for the GRA9 region is temporarily unavailable. Customers Impact : Customers are temporarily unable to create, start, manage their Public Cloud instances and create or attach new volumes. Instances already running are not impacted. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

Investigating: We are currently experiencing an event affecting our Public Cloud Network API offer in GRA9 region.

Start time : 08/04/2026 09:06 UTC

Our teams are fully committed to investigating this issue and working towards a resolution as soon as possible. As investigations are ongoing, we will share any new findings or updates with you as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

Resolved: We are pleased to inform you that the incident affecting our Containers & Orchestration offer in GRA9 region has been resolved.

Start time : 08/04/2026 09:06 UTC End time : 08/04/2026 10:12 UTC Root Cause : This was caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/vwqd4hm52ytq

We apologize for any inconvenience caused and appreciate your understanding.

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific region GRA9.

Here are some supplementary details :

Start time : 08/04/2026 09:06 UTC Impacted Service(s) : Managed Kubernetes Service clusters in GRA9 are temporarily facing latency. Customers Impact : Customers are temporarily facing latency while trying to access their Managed Kubernetes Service clusters. Root Cause : This incident is caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/vwqd4hm52ytq Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

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 are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.

Here are some supplementary details : Start time : 16/03/2026 08:00 UTC Impacted 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. 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. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

If you have 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: 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 are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.

Here are some supplementary details : Start time : 16/03/2026 08:00 UTC Impacted 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. 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. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

If you have 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: 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 are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.

Here are some supplementary details : Start time : 16/03/2026 08:00 UTC Impacted 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. 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. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

If you have 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: 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 are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.

Here are some supplementary details : Start time : 16/03/2026 08:00 UTC Impacted 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. 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. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

If you have 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: 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 are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.

Here are some supplementary details : Start time : 16/03/2026 08:00 UTC Impacted 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. 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. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

If you have 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: 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 are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.

Here are some supplementary details : Start time : 16/03/2026 08:00 UTC Impacted 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. 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. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.