Is Public Cloud down?
Last checked 7m agoActive incident: [GLOBAL][Databases] - PostgreSQL 18 and PostGIS Compatibili…
Public Cloud is reporting degraded performance right now (last checked 7m ago). Services are up but slower or partially failing.
Real-time Public Cloud status, recent outages, and incident history — pulled directly from Public Cloud's official status page at https://public-cloud.status-ovhcloud.com every 5 minutes. Pingoru tracks 597 Public Cloud services and has captured 118 incidents in the last 90 days (98.83% uptime). Get email, Slack, Discord, or webhook alerts the moment Public Cloud reports a new incident — free for 5 monitors, no credit card.
Active incident 1
- BHSDEGRAEU-SOUTH-MILAP-SOUTH-MUMEU-WEST-PARRBXSBGSGPUK
Timeline · 4 updates
- identified · Mar 30, 2026, 12:36 PM UTC
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 · Apr 09, 2026, 02:08 PM UTC
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 · Jun 11, 2026, 08:45 AM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : 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. Ongoing Actions : We are closely monitoring the situation while the PostGIS team works on a resolution. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- monitoring · Jul 08, 2026, 02:22 PM 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 appreciate your understanding.
Latest: 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 introduce…
-
Recent outages & incidents
Past 90 days- GRA1GRA3GRA9GRA11
Timeline · 2 updates
- identified · Sep 13, 2026, 09:24 AM UTC
We are currently experiencing an incident affecting our Public Cloud offering in the GRA1/3/9/11 regions. The root cause has been identified. Please find the details of this incident below : Start time : 13/09/2026 09:02 UTC Impacted Service(s) : Some instances in the GRA region are unavailable. Customers Impact : Customers are temporarily unable to access their instances located on the specified regions. Root Cause : This incident is caused by an unexpected infrastructure malfunction. Ongoing Actions : Our teams are actively working 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.
- resolved · Sep 13, 2026, 10:39 AM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 13/09/2026 09:02 UTC End time : 13/09/2026 10:06 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Latest: We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 13/09/2026 09:02 UTC End time : 13/09/2026 10:06 UTC Root C…
-
- SBG5SBG7
Timeline · 4 updates
- identified · Sep 10, 2026, 10:22 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific SBG5 / SBG7 regions. Here are some supplementary details : Start time : 10/09/2026 22:13 UTC Impacted Service(s) : Some instances in the SBG5 / SBG7 regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified regions. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. 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 · Sep 11, 2026, 03:31 AM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Some instances are now accessible again. Ongoing Actions : Our teams are actively working to restore the remaining instances 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 · Sep 11, 2026, 01:08 PM UTC
We have new information regarding the incident that affects your service(s). Please find below an update on the situation : Update : Most instances are once again accessible. Impacted Service(s) : Some instances in the SBG5 / SBG7 regions are still temporarily unreachable. Customers Impact : Some customers are still temporarily unable to access instances located in the specified regions. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : Our teams are actively working to restore the remaining instances as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved · Sep 11, 2026, 10:04 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 10/09/2026 22:13 UTC End time : 11/09/2026 21:00 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Latest: We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 10/09/2026 22:13 UTC End time : 11/09/2026 21:00 UTC Root C…
-
- GRA11
Timeline · 2 updates
- investigating · Sep 06, 2026, 10:13 AM UTC
We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary availability issue in the GRA11 region. Here are some supplementary details : Start time : 06/09/2026 09:00 UTC Impacted Service(s) : The Managed Kubernetes Service cluster is experiencing high load. Customers Impact : Customers are experiencing degraded service performance and are currently unable to provision new resources. 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.
- resolved · Sep 06, 2026, 11:48 AM UTC
We are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved. Start time : 06/09/2026 09:00 UTC End time : 06/09/2026 10:45 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
Latest: We are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved. Start time : 06/09/2026 09:00 UTC End time : 06/09/2026 10:45 UT…
-
- GRA1GRA11
Timeline · 3 updates
- investigating · Sep 03, 2026, 03:39 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Storage offer on the specific GRA1 and GRA11 region. Here are some supplementary details : Start time : 03/09/2026 15:16 UTC Impacted Service(s) : Some Block Storage services are temporarily unavailable. Customers Impact : Some customers may temporarily experience degraded performance on their block storage services. Root Cause : A service disruption occurred due to an unexpected infrastructure failure 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 · Sep 03, 2026, 03:44 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Storage offer on the specific GRA1 and GRA11 region. Here are some supplementary details : Start time : 03/09/2026 15:16 UTC Impacted Service(s) : Some Block Storage services are temporarily unavailable. Customers Impact : Some customers may temporarily experience degraded performance on their block storage services. Root Cause : A service disruption occurred due to an unexpected infrastructure failure 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.
- resolved · Sep 03, 2026, 07:01 PM UTC
We are pleased to inform you that the incident affecting our Storage offering has been resolved. Start time : 03/09/2026 15:16 UTC End time : 03/09/2026 18:41 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.
Latest: We are pleased to inform you that the incident affecting our Storage offering has been resolved. Start time : 03/09/2026 15:16 UTC End time : 03/09/2026 18:41 UTC Root Cause : A se…
-
- BHSDEGRAEU-WEST-PARSBGSGPUKWAWEU-SOUTH-MILRBX
Timeline · 3 updates
- investigating · Sep 03, 2026, 10:18 AM UTC
We are currently experiencing an incident affecting our MongoDB Database offering. Please find the details of this incident below : Start time : 25/08/2026 00:00 UTC Impacted Service(s) : MongoDB services are currently unable to perform their daily backups. Customers Impact : Customers using the affected MongoDB services are currently unable to perform their daily backups. Ongoing Actions : Our teams are investigating the issue to determine its root cause and restore the backup functionality. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- monitoring · Sep 03, 2026, 02:04 PM UTC
Service has been fully restored since 03/09/2026 13:00 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 25/08/2026 00:00 UTC Impacted Service(s) : MongoDB services were unable to perform their daily backups. Customers Impact : Customers using the affected MongoDB services were unable to perform their daily backups. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
- resolved · Sep 04, 2026, 07:40 AM UTC
We are pleased to inform you that the incident affecting our MongoDB Database offering has been resolved. Start time : 25/08/2026 00:00 UTC End time : 03/09/2026 13:00 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Latest: We are pleased to inform you that the incident affecting our MongoDB Database offering has been resolved. Start time : 25/08/2026 00:00 UTC End time : 03/09/2026 13:00 UTC Root Cau…
-
See the full Public Cloud outage history
68 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Public Cloud outage history →Or sign up free to get alerts when Public Cloud breaks · 10 free monitors · No credit card
- Started Sep 13, 2026, 09:24 AM UTC · Resolved Sep 13, 2026, 10:39 AM UTC · 1h 14m
- Started Sep 10, 2026, 10:22 PM UTC · Resolved Sep 11, 2026, 10:04 PM UTC · 23h 41m
- Started Sep 06, 2026, 10:13 AM UTC · Resolved Sep 06, 2026, 11:48 AM UTC · 1h 35m
- Started Sep 03, 2026, 03:39 PM UTC · Resolved Sep 03, 2026, 07:01 PM UTC · 3h 22m
- Started Sep 03, 2026, 10:18 AM UTC · Resolved Sep 04, 2026, 07:40 AM UTC · 21h 22m
- Started Aug 31, 2026, 05:09 PM UTC · Resolved Aug 31, 2026, 06:09 PM UTC · 59m
- Started Aug 28, 2026, 11:19 PM UTC · Resolved Aug 28, 2026, 11:19 PM UTC · —
- Started Aug 25, 2026, 09:25 PM UTC · Resolved Aug 27, 2026, 01:08 PM UTC · 1d 15h