Is Public Cloud down?

Last checked 8m ago
Current status
Public Cloud is having a partial outage

2 active incidents: [GRA/RBX/DE][Storage and Backups] - Object Storage Incident…, [GLOBAL][Databases] - PostgreSQL 18 and PostGIS Compatibili…

Official status page: https://public-cloud.status-ovhcloud.com · Polled every 5 minutes · 576 components tracked

Public Cloud is reporting a partial outage right now (last checked 8m ago). Some components are affected; others remain operational.

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 576 Public Cloud services and has captured 105 incidents in the last 90 days (99.14% uptime). Get email, Slack, Discord, or webhook alerts the moment Public Cloud reports a new incident — free for 5 monitors, no credit card.

Users who monitor Public Cloud also follow these Web Hosting services: Gandi IONOS Germany Expo Shippo FormAssembly Courier EasySpace Appwrite Endless Group Digital Pacific View all 6,000+ providers
Public Cloud uptime 99.14% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Active incidents 2

  1. Ongoing ● 22d 7h
    Started May 22, 2026, 03:04 PM UTC
    GRADERBX
    Timeline · 3 updates
    • investigating · May 22, 2026, 03:04 PM UTC

      We are currently investigating an incident affecting our Storage and Backups offering, which is causing temporary functionality issue in GRA/RBX/DE regions Here are some supplementary details : Start time : 13/05/2026 00:00 UTC Impacted Service(s) : Delay in lifecycle rules execution for regions GRA, RBX and DE Customers Impact : Some customers might face delay in lifecycle rules execution in specified regions. 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 · May 25, 2026, 08:58 AM UTC

      We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : The incident is still under investigation by our technical teams, who are working to determine its cause and implement a fix. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

    • identified · Jun 11, 2026, 10:05 AM UTC

      We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Storage and Backups offering in GRA/RBX/DE regions. Here are some supplementary details : Start time : 13/05/2026 00:00 UTC Impacted Service(s) : Delay in lifecycle rules execution for regions GRA, RBX and DE. Customers Impact : Some customers might face delay in lifecycle rules execution in specified regions. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : Processing has been improved and most of the backlog has been cleared. Some workloads with a very high number of pending events may still experience delays while we continue optimizing processing. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

    Latest: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Storage and Backups offering in GRA/RBX/DE regions. Here are some supple…

  2. Ongoing ● 75d 9h
    Started Mar 30, 2026, 12:36 PM UTC
    BHSDEGRAEU-SOUTH-MILAP-SOUTH-MUMEU-WEST-PARRBXSBGSGPUK
    Timeline · 3 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.

    Latest: 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 rele…

Recent outages & incidents

Past 90 days
  1. Resolved 3h 43m
    Started Jun 11, 2026, 12:32 PM UTC · Resolved Jun 11, 2026, 04:16 PM UTC
    Data & Analytics || Data Platform
    Timeline · 2 updates
    • investigating · Jun 11, 2026, 12:32 PM UTC

      We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary availability issue in GLOBAL regions. Here are some supplementary details : Start time : 11/06/2026 09:00 UTC Impacted Service(s) : Some jobs cannot be executed on the Data Platform. Customers Impact : Some customers cannot run some jobs, causing delays in data processing and dependent workflows. 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 · Jun 11, 2026, 04:16 PM UTC

      We are pleased to inform you that the incident affecting our Data & Analytics offering has been resolved. Start time : 10/06/2026 12:00 UTC End time : 11/06/2026 13:00 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 Data & Analytics offering has been resolved. Start time : 10/06/2026 12:00 UTC End time : 11/06/2026 13:00 UTC Root Cau…

  2. Resolved 2h 41m
    Started Jun 10, 2026, 03:20 PM UTC · Resolved Jun 10, 2026, 06:01 PM UTC
    EU-WEST-PAR-AEU-WEST-PAREU-WEST-PAR-BEU-WEST-PAR-CEU-WEST-PAREU-WEST-PAREU-WEST-PAREU-WEST-PAREU-WEST-PAREU-WEST-PAR
    Timeline · 2 updates
    • identified · Jun 10, 2026, 03:20 PM UTC

      We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Public Cloud offer on the specific EU-WEST-PAR region. Here are some supplementary details : Start time : 09/06/2026 07:00 UTC Impacted Service(s) : Nodes located in EU-WEST-PAR region may experience packets drop while communicating with their controlplanes and the Internet. Customers Impact : Customer are temporarily facing connectivity issues with their nodes located in the specified region. 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.

    • resolved · Jun 10, 2026, 06:01 PM UTC

      We are pleased to inform you that the incident affecting our Dedicated Servers offering has been resolved. Start time : 09/06/2026 07:00 UTC End time : 10/06/2026 17:55 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 Dedicated Servers offering has been resolved. Start time : 09/06/2026 07:00 UTC End time : 10/06/2026 17:55 UTC Root Ca…

  3. Resolved 7h 1m
    Started Jun 10, 2026, 01:25 AM UTC · Resolved Jun 10, 2026, 08:26 AM UTC
    SBG5
    Timeline · 3 updates
    • identified · Jun 10, 2026, 01:25 AM UTC

      We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Block storage offer in SBG5. Please find the details of this incident below : Start time : 10/06/2026 00:50 UTC Impacted Service(s) : Block storage service is experiencing degraded performance. Customers Impact : Customers may experience increased latency, slower response times, or intermittent errors when accessing or managing data stored on the affected Block Storage. 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.

    • monitoring · Jun 10, 2026, 01:30 AM UTC

      Service has been fully restored since 10/06/2026 01:26 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 10/06/2026 00:50 UTC Impacted Service(s) : Block Storage service experienced degraded performance. Customers Impact : Customers may have experienced increased latency, slower response times, or intermittent errors when accessing or managing data stored on the affected Block Storage. We apologize for any inconvenience caused and appreciate your understanding.

    • resolved · Jun 10, 2026, 08:26 AM UTC

      We are pleased to inform you that the incident affecting our Block storage offering has been resolved. Start time : 10/06/2026 00:50 UTC End time : 10/06/2026 07:10 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 Block storage offering has been resolved. Start time : 10/06/2026 00:50 UTC End time : 10/06/2026 07:10 UTC Root Cause …

  4. Resolved 11h 14m
    Started Jun 09, 2026, 01:50 PM UTC · Resolved Jun 10, 2026, 01:05 AM UTC
    GRA1GRA3GRA9
    Timeline · 4 updates
    • identified · Jun 09, 2026, 01:50 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 GRA1/3/9 regions. Here are some supplementary details : Start time : 09/06/2026 13:35 UTC Impacted Service(s) : All or some instances in the GRA1/3/9 regions are unreachable. Customers Impact : Some customers are temporarily unable to access and use their Public Cloud instances located in 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 · Jun 09, 2026, 04:51 PM 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 no longer impacted by the incident. 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 · Jun 09, 2026, 10:00 PM UTC

      Ongoing Actions : 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 · Jun 10, 2026, 01:05 AM UTC

      We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 09/06/2026 13:35 UTC End time : 10/06/2026 00:30 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 : 09/06/2026 13:35 UTC End time : 10/06/2026 00:30 UTC Root C…

  5. Resolved 2h 32m
    Started Jun 06, 2026, 04:28 PM UTC · Resolved Jun 06, 2026, 07:00 PM UTC
    GRA5GRA7GRA11
    Timeline · 2 updates
    • identified · Jun 06, 2026, 04:28 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 GRA region. Here are some supplementary details : Start time : 06/06/2026 15:06 UTC Impacted Service(s) : Some instances in the GRA5 - GRA7 - GRA11 region are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified region. 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 · Jun 06, 2026, 07:00 PM UTC

      We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 06/06/2026 15:06 UTC End time : 06/06/2026 18:55 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 Compute - Instance offering has been resolved. Start time : 06/06/2026 15:06 UTC End time : 06/06/2026 18:55 UTC Root C…

See the full Public Cloud outage history

69 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

Outage history

Past 90 days · 74 incidents View full outage history →