CHYP.ai · ORBIT // Cloudy_Day Security Suite

Cloud platforms

Degraded / minor incident OVHcloud status

ovhcloud.com · Official status page (Statuspage-compatible JSON)

Official status

Degraded / minor incident Degraded / minor incident

Minor Service Outage

Active incidents (3)

  1. [GLOBAL][AI & Machine Learning] - AI Endpoint Incident Notification major monitoring · started

    Affects: AI & Machine Learning || AI Endpoint

    1. · monitoring
      We would like to inform you that our service has been fully restored as of 20/11/2026 07:12 UTC. Monitoring is still in place to ensure long-term stability. Please find the details of this incident below : <b>Start time :</b> 20/11/2026 06:25 UTC <b>Impacted Service(s) :</b> AI Endpoints service was temporarily unavailable. <b>Customers Impact :</b> Customers may have experienced API errors when calling AI Endpoints models. We apologize for any inconvenience caused and appreciate your understanding.
    2. · investigating
      We are currently investigating an incident affecting our AI & Machine Learning offering, which is causing temporary availability issue on AI Endpoint . Here are some supplementary details : <b>Start time :</b> 20/11/2026 06:25 UTC <b>Impacted Service(s) :</b> The AI Endpoints is temporarily unavailable. <b>Customers Impact :</b> Customers may temporarily experience unavailability when using the AI endpoints. <b>Ongoing Actions :</b> 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.

    Official notice ↗ · Replay & discuss

  2. [US-WEST-OR][Storage] - Cloud Archive incident notification major identified · started

    Affects: US-WEST-OR

    1. · identified
      We are currently experiencing an incident affecting our Cloud Archive offering in the US-WEST-OR region. The root cause has been identified. Please find the details of this incident below : <b>Start time :</b> 19/11/2026 16:30 UTC <b>Impacted Service(s) :</b> The Cloud Archive service is experiencing an increased error rate in the US-WEST-OR region. <b>Customers Impact :</b> Customers may experience errors when storing or retrieving their archived data. <b>Root Cause :</b> This incident is caused by a software issue. <b>Ongoing Actions :</b> 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.
    2. · monitoring
      We would like to inform you that our service has been fully restored as of 19/11/2026 21:45 UTC. Monitoring is still in place to ensure long-term stability. Please find the details of this incident below : <b>Start time :</b> 19/11/2026 16:30 UTC <b>Impacted Service(s) :</b> The Cloud Archive service experienced an increased error rate in the US-WEST-OR region. <b>Customers Impact :</b> Customers may have experienced errors when storing or retrieving their archived data. We apologize for any inconvenience caused and appreciate your understanding.
    3. · investigating
      We are currently experiencing an incident affecting our Cloud Archive offering, which is causing temporary availability issues in the US-WEST-OR region. Please find the details of this incident below : <b>Start time :</b> 19/11/2026 16:30 UTC <b>Impacted Service(s) :</b> The Cloud Archive service is experiencing an increased error rate in the US-WEST-OR region. <b>Customers Impact :</b> Customers may experience errors when storing or retrieving their archived data. <b>Ongoing Actions :</b> Our teams are investigating to determine the origin of the incident to fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

    Official notice ↗ · Replay & discuss

  3. [GLOBAL][Databases] - PostgreSQL 18 and PostGIS Compatibility Issue minor monitoring · started

    Affects: BHS, DE, GRA, EU-SOUTH-MIL, AP-SOUTH-MUM, EU-WEST-PAR, RBX, SBG, SGP, UK, US-EAST-VA, US-WEST-OR

    1. · monitoring
      We have new information regarding the incident that affected your service(s). Please find below an update on the situation: <b>Update :</b> 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. <b>Ongoing Actions :</b> The incident has been identified and corrected. It is being closely monitored to ensure long-term stab
    2. · identified
      We have new information regarding the incident that affected your service(s). Please find below an update on the situation: <b>Update : </b> 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. <b>Ongoing Actions :</b> We are closely monitoring the situation while the PostGIS team works on a resolution. We will keep yo
    3. · 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.
    4. · identified
      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. Here are some supplementary details : <b>Start time :</b> 16/03/2026 08:00 UTC <b>Impacted Service(s) :</b> 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. <b>Root Cause :</b> This incident is caused by PostGIS extension current version 3.5. <b>Ongoing Actions :</b> The PostGIS team needs to fix this bug and release a new version of the extension (v3.6). In the meantime, our serv

    Official notice ↗ · Replay & discuss

Components 599/600 operational

  • US-WEST-OR partial outage
  • BHS operational
  • BHS operational
  • DE operational
  • SGP1 operational
  • BHS operational
  • DE1 operational
  • WAW1 operational
  • BHS operational
  • GRA1 operational
  • DE1 operational
  • SYD1 operational
  • UK1 operational
  • BHS1 operational
  • BHS operational
  • US-EAST-VA-1 operational
  • BHS operational
  • BHS operational
  • BHS operational
  • BHS operational
  • BHS operational
  • BHS operational
  • BHS operational
  • BHS operational
  • BHS operational
  • BHS1 operational
  • BHS1 operational
  • BHS1 operational
  • BHS1 operational
  • BHS1 operational
  • BHS1 operational
  • RBX-ARCHIVE operational
  • RBX-A operational
  • AP-SOUTHEAST-SYD-2 operational
  • EU-WEST-LZ-AMS operational
  • AF-NORTH-LZ-RBA operational
  • US-WEST-LZ-DEN operational
  • US-EAST-LZ-ATL operational
  • BHS1 operational
  • BHS1 operational
  • AP-SOUTH-MUM-1 operational
  • EU-WEST-PAR-A operational
  • EU-SOUTH-LZ-LIS operational
  • AP-SOUTHEAST-SGP operational
  • EU-NORTH-LZ-CPH operational
  • EU-CENTRAL-LZ-BUH operational
  • US-CENTRAL-LZ-SLC operational
  • AP-SOUTH-MUM operational
  • BHS operational
  • BHS operational
  • EU-SOUTH-MIL-A operational
  • AP-SOUTH-MUM operational
  • EU-WEST-PAR operational
  • AP-SOUTH-MUM operational
  • AF-CENTRAL-LZ-ABJ operational
  • AP-SOUTH-MUM-1 operational
  • AP-SOUTH-LZ-AKL operational
  • SA-WEST-LZ-SCL operational
  • DE operational
  • GRA operational
  • GRA operational
  • BHS5 operational
  • GRA operational
  • GRA1 operational
  • GRA operational
  • BHS3 operational
  • GRA operational
  • US-WEST-OR-1 operational
  • DE operational
  • GRA operational
  • DE operational
  • DE operational
  • DE operational
  • DE operational
  • DE operational
  • DE operational
  • DE operational
  • BHS3 operational
  • BHS3 operational
  • BHS3 operational
  • BHS3 operational
  • BHS5 operational
  • BHS3 operational
  • BHS3 operational
  • BHS operational
  • EU-WEST-LZ-BRU operational
  • AP-SOUTHEAST-SYD-2 operational
  • SGP2 operational
  • EU-CENTRAL-LZ-PRG operational
  • US-WEST-LZ-LAX operational
  • BHS3 operational
  • BHS3 operational
  • EU-WEST-PAR-B operational
  • AP-SOUTH-MUM-1 operational
  • EU-SOUTH-LZ-MAD operational
  • US-EAST-LZ-BOS operational
  • AI & Machine Learning || AI Endpoint operational
  • AP-SOUTHEAST-SYD operational
  • EU-NORTH-LZ-HEL operational
  • US-CENTRAL-LZ-STL operational
  • AP-SOUTHEAST-SYD-2 operational
  • GRA operational
  • GRA operational
  • EU-SOUTH-MIL-B operational
  • AP-SOUTH-MUM operational
  • EU-SOUTH-MIL operational
  • BHS3 operational
  • GRA operational
  • EU-WEST-LIM operational
  • GRA3 operational
  • BHS5 operational
  • SBG5 operational
  • GRA operational
  • DE operational
  • GRA operational
  • GRA operational
  • GRA operational
  • GRA operational
  • GRA operational
  • GRA operational
  • GRA operational
  • BHS5 operational
  • BHS5 operational
  • BHS1 operational
  • BHS5 operational
  • BHS5 operational
  • DE1 operational
  • BHS5 operational
  • BHS5 operational
  • DE operational
  • GRA2 operational
  • EU-SOUTH-LZ-MIL operational
  • US-EAST-LZ-CHI operational
  • US-WEST-LZ-PAO operational
  • BHS5 operational
  • BHS5 operational
  • EU-WEST-LZ-DLN operational
  • EU-WEST-PAR-C operational
  • CA-EAST-TOR operational
  • EU-NORTH-LZ-OSL operational
  • EU-CENTRAL-LZ-SOF operational
  • BHS5 operational
  • EU-SOUTH-MIL-C operational
  • AP-SOUTH-MUM operational
  • BHS5 operational
  • GRA3 operational
  • DE1 operational
  • BHS3 operational
  • DE1 operational
  • SBG7 operational
  • DE1 operational
  • DE1 operational
  • RBX operational
  • DE1 operational
  • DE1 operational
  • US-EAST-LZ-DAL operational
  • DE1 operational
  • DE1 operational
  • EU-NORTH-LZ-STO operational
  • EU-WEST-LZ-LUX operational
  • CA-EAST-BHS operational
  • EU-WEST-PAR operational
  • EU-WEST-PAR operational
  • EU-WEST-PAR operational
  • US-WEST-LZ-PHX operational
  • DE1 operational
  • EU-SOUTH-MIL operational
  • EU-SOUTH-MIL operational
  • EU-SOUTH-MIL operational
  • EU-SOUTH-MIL operational
  • EU-SOUTH-MIL operational
  • EU-SOUTH-MIL operational
  • EU-SOUTH-MIL operational
  • EU-WEST-PAR operational
  • EU-SOUTH-MIL operational
  • BHS7 operational
  • DE1 operational
  • GRA5 operational
  • GRA5 operational
  • GRA1 operational
  • BHS5 operational
  • GRA1 operational
  • SBG operational
  • SBG operational
  • GRA1 operational
  • SBG operational
  • GRA1 operational
  • GRA5 operational
  • GRA1 operational
  • GRA1 operational
  • US-EAST-LZ-MIA operational
  • GRA1 operational
  • GRA1 operational
  • US-WEST-LZ-SEA operational
  • EU-WEST-LZ-MNC operational
  • EU-CENTRAL-WAW operational
  • EU-SOUTH-MIL operational
  • EU-WEST-PAR operational
  • AP-SOUTH-MUM operational
  • AP-SOUTH-MUM operational

Source: Official status page (Statuspage-compatible JSON) · https://public-cloud.status-ovhcloud.com. Fetched passively from the provider's public status page; refreshed about every minute while people are looking.

How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.

Where to next