Is Public Cloud down?

Last checked 9m ago
Current status
Public Cloud has degraded performance

2 active incidents: [GLOBAL][Public Cloud] - AI & Machine Learning maintenance…, [GLOBAL][Databases] - PostgreSQL 18 and PostGIS Compatibili…

Get alerts when Public Cloud breaks → View Public Cloud outage history →

Free · no credit card

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

Public Cloud is reporting degraded performance right now (last checked 9m 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 598 Public Cloud services and has captured 124 incidents in the last 90 days (99.20% 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.20% uptime · past 90 days
Mon Wed Fri
MayJunJul
Less More

Active incident 1

  1. [GLOBAL][Databases] - PostgreSQL 18 and PostGIS Compatibility Issue
    Ongoing ● 122d 18h
    Started Mar 30, 2026, 12:36 PM UTC
    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
  1. [GRA][Storage] - Object Storage incident notification
    Resolved —
    Started Jul 29, 2026, 01:06 PM UTC · Resolved Jul 29, 2026, 01:06 PM UTC
    GRA
    Timeline · 1 update
    • resolved · Jul 29, 2026, 01:06 PM UTC

      We had an incident on our Object Storage offer in GRA region which has now been resolved. Here are some supplementary details : Start time : 29/07/2026 06:00 UTC End time : 29/07/2026 11:00 UTC Impacted Service(s) : Slowness and 504 error were observed for object storage located in GRA. Customers Impact : Customers were temporarily facing slowness and 504 error when trying to access and use their objects in the specified region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.

    Latest: We had an incident on our Object Storage offer in GRA region which has now been resolved. Here are some supplementary details : Start time : 29/07/2026 06:00 UTC End time : 29/07/2…

  2. [WAW1][Compute - Instance] - Some instances incident notification
    Resolved 8m
    Started Jul 28, 2026, 05:12 PM UTC · Resolved Jul 28, 2026, 05:21 PM UTC
    WAW1
    Timeline · 2 updates
    • identified · Jul 28, 2026, 05:12 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 WAW1 region. Here are some supplementary details : Start time : 28/07/2026 17:06 UTC Impacted Service(s) : Some instances in the WAW1 region are unreachable. Customers Impact : Some customers are temporarily unable to access instances 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 · Jul 28, 2026, 05:21 PM UTC

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

  3. [GRA11][Network] - Load Balancer incident notification
    Resolved 1d 2h
    Started Jul 27, 2026, 12:52 PM UTC · Resolved Jul 28, 2026, 03:15 PM UTC
    GRA11GRA11
    Timeline · 4 updates
    • identified · Jul 27, 2026, 12:52 PM UTC

      We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer in the specific GRA11 region. Here are some supplementary details : Start time : 27/07/2026 07:41 UTC Impacted Service(s) : Creation of Public Cloud instances on GRA11 LoadBalancer is temporarily unavailable. Customers Impact : Customers are temporarily unable to create new Public Cloud instances on LoadBalancer. 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 · Jul 28, 2026, 11:25 AM UTC

      We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Our teams are currently working on a fix to resolve the issue. 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 · Jul 28, 2026, 12:13 PM UTC

      We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : The majority of customers 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.

    • resolved · Jul 28, 2026, 03:15 PM UTC

      We are pleased to inform you that the incident affecting our Load Balancer offering has been resolved. Start time : 27/07/2026 07:41 UTC End time : 28/07/2026 14: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 Load Balancer offering has been resolved. Start time : 27/07/2026 07:41 UTC End time : 28/07/2026 14:45 UTC Root Cause …

  4. [UK1][Compute - Instance] - Some instances incident notification
    Resolved 2h 5m
    Started Jul 27, 2026, 06:33 AM UTC · Resolved Jul 27, 2026, 08:39 AM UTC
    UK1
    Timeline · 2 updates
    • identified · Jul 27, 2026, 06:33 AM UTC

      We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific UK1 region. Here are some supplementary details : Start time : 27/07/2026 06:19 UTC Impacted Service(s) : Some instances in the UK1 region are unreachable. Customers Impact : Some customers are temporarily unable to access instances 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 · Jul 27, 2026, 08:39 AM UTC

      We are pleased to inform you that the incident affecting our Compute - Instance offering in UK1 region has been resolved. Start time : 27/07/2026 06:19 UTC End time : 27/07/2026 07:40 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 in UK1 region has been resolved. Start time : 27/07/2026 06:19 UTC End time : 27/07/2026 07…

  5. [EU-WEST-PAR][Storage] - Object storage S3 Standard Incident Notification
    Resolved 17h 43m
    Started Jul 23, 2026, 07:14 PM UTC · Resolved Jul 24, 2026, 12:58 PM UTC
    EU-WEST-PAR-AEU-WEST-PAR-BEU-WEST-PAR-C
    Timeline · 3 updates
    • investigating · Jul 23, 2026, 07:14 PM UTC

      We are currently investigating an incident affecting our Storage offering, which is causing temporary issue in the EU-WEST-PAR region. Here are some supplementary details : Start time : 23/07/2026 18:00 UTC Impacted Service(s) : Intermittent HTTP 503 errors may affect object upload and download operations. Customers Impact : Customers may experience issues downloading or uploading their objects due to 503 errors. 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.

    • monitoring · Jul 23, 2026, 11:30 PM UTC

      We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : The services s are operational again since 23/07/2026 23:15 UTC. Ongoing Actions : Our team will monitor the situation. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

    • resolved · Jul 24, 2026, 12:58 PM UTC

      We are pleased to inform you that the incident affecting our Storage offering has been resolved. Start time : 23/07/2026 18:00 UTC End time : 23/07/2026 23:15 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 Storage offering has been resolved. Start time : 23/07/2026 18:00 UTC End time : 23/07/2026 23:15 UTC Root Cause : A se…

See the full Public Cloud outage history

74 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 · 78 incidents View full outage history →