Some systems are experiencing issues
Maintenance
Scheduled maintenance — Paris (PAR) hypervisor reboot
  • Affected components: Paris (PAR) region — Applications & Add-ons (subset)
  • Customer impact window: from 2026-06-30 20:30 (Europe/Paris, CEST/UTC+2) — possible one-time restart during migration (one week ahead)

We will carry out scheduled maintenance on part of our Paris (PAR) infrastructure. All times are Europe/Paris (CEST, UTC+2).

To prepare hypervisor reboot, affected applications and add-ons are migrated to other hosts on 30 June starting 20:30**. During this migration, each impacted application or add-on restarts once (typically a few seconds to a couple of minutes). This is the only customer-visible impact.

On 7 July, 12:00 → 14:00, we will then reboot the underlying hypervisors. As the affected workloads have already been moved off, no further interruption is expected during this reboot window.

If your application is impacted and you would rather move it yourself in advance, you can redeploy/restart it at any time before 30 June 18:00. Impacted customers are also contacted individually.

Scheduled maintenance — Paris (PAR) hypervisor reboot

Affected components: Paris (PAR) region — Applications & Add-ons (subset)

  • Customer impact window: from 2026-07-02 20:30 (Europe/Paris, CEST/UTC+2) — possible one-time restart during migration (one week ahead)

We will carry out scheduled maintenance on part of our Paris (PAR) infrastructure. All times are Europe/Paris (CEST, UTC+2).

Most affected applications and add-ons are migrated to other hosts on 2 July starting 20:30; during this migration each impacted workload restarts once (a few seconds to a couple of minutes).

On 9 July, 12:00 → 14:00, we will reboot the underlying hypervisors.

Impacted customers are also contacted individually.

Scheduled maintenance — Paris (PAR) PostgreSQL dev cluster downtime

Affected components: public Dev cluster (downtime)

  • Hypervisor reboot window: 2026-07-09 12:00 → 14:00 (Europe/Paris, CEST/UTC+2)
  • PostgreSQL Dev cluster downtime: ≈ 1 hour within the 12:00 → 14:00 window

We will carry out scheduled maintenance on part of our Paris (PAR) infrastructure. All times are Europe/Paris (CEST, UTC+2).

On 9 July, 12:00 → 14:00, we reboot the underlying hypervisors which will cause the PostgreSQL public Dev cluster to undergo maintenance with downtime within this window: databases hosted on the Dev cluster will be unavailable for approximately one hour (about half of the 12:00 → 14:00 window). A full backup is taken beforehand, and service is restored as soon as the operation completes.

Past Incidents

Friday 26th June 2026

No incidents reported

Thursday 25th June 2026

No incidents reported

Wednesday 24th June 2026

Infrastructure [PAR] Elevated datacenter temperatures during heatwave

Due to the ongoing heatwave in Paris, ambient temperatures in one of our availability zones in the Paris region have risen above their usual operating range. The datacenter operations teams are actively managing the cooling infrastructure and have the situation under close surveillance.

At this time there is no impact on our services, and all systems are operating normally. We are publishing this update for transparency and are monitoring temperature levels continuously alongside the datacenter teams.

We will update this incident if the situation changes. No action is required from our customers.

  • The datacenter operations team has taken action and isolated the issue with the cooling system. A technician will come tomorrow morning to apply a long-term fix.

    In the meantime, the datacenter operations team is closely monitoring the temperature of the rooms and working to keep them as cool as possible so that services keep running smoothly.

  • We have now completed all the preventive actions available on our side to protect Clever Cloud services in the affected availability zone.

    All applications have already been redeployed onto other availability zones. For databases, we have contacted customers who have a disaster recovery plan (PRA) and a primary (leader) instance in this availability zone, so that their follower instances in other zones can be promoted. If you wish to migrate your database yourself, you can do so directly from the Console.

    The situation is now under close watch, and we are already seeing an improvement in the conditions of the affected zone. We will continue to monitor closely and will keep this incident updated should any new event occur.

    No further action is required from customers at this time.

  • Main database has been migrated, the APIs are UP. We start migrating the postgresql add-on provider database to ensure maximum uptime in case of datacenter failure.

  • We are still working on migrating the main API database. API and deployments downtime are to be expected

  • [12: 55 CEST] The API maintenance is now completed, some unavailability was detected around 12h40 - 12h45

  • The maintenance has started.

    The Clever Cloud API is now in read-only mode and may be briefly unavailable while the API and deployment stack are redeployed.

    Running applications remain unaffected.

  • We will be redeploying the Clever Cloud API along with part of the deployment stack. During this maintenance window the API will be in read-only mode, and may be briefly unavailable for a few minutes. While the maintenance is in progress you may be unable to create, modify, or trigger new deployments, and some API calls may temporarily fail or return read-only responses.

    Already-running applications and add-ons are not affected and will continue to operate normally.

    No action is required from our customers. We recommend avoiding deployments and configuration changes during the maintenance window.

  • As a preventive measure while the heatwave continues, we are proactively migrating part of the workloads running in the affected availability zone to other availability zones in the Paris region. Redistributing the compute load in this way lowers the amount of heat generated in the zone and helps our cooling infrastructure keep ambient temperatures within their normal operating range. These migrations are being carried out gradually and under close supervision.

    The large majority of applications will not be affected. Where possible, we recommend ensuring your applications are configured for automatic restart and redundancy.

    Our teams continue to monitor temperature levels continuously alongside the datacenter operations teams, and we will keep this incident updated as the situation evolves.

    • Tuesday 23rd June 2026

    No incidents reported

    Monday 22nd June 2026

    Infrastructure [MTL] An hypervisor is unreachable

    An hypervisor is unreachable on the MTL region since 15:25 UTC. We are investigating the root cause. Add-ons hosted on this node are unreachable, applications are redeploying.

  • The incident is over.

  • The server has been recovered and customer services are recovering. We continue to monitor the situation.

  • We are having troubles getting the hypervisor back up. We escalated the issue to OVHcloud to check for hardware issues.

  • The hypervisor crashed. We are trying to reboot it.

    • Sunday 21st June 2026

    No incidents reported

    Saturday 20th June 2026

    No incidents reported