Incident History
Full history of incidents.
August 2026
We have identified an issue affecting the NetworkGroups service. Some users may experience difficulties managing their network configurations. Our team is working to resolve the problem. We will provide further updates as we progress.
The central Clever Cloud API has stopped responding. It appears the issue is related to database access. We are investigating.
During this time you may experience:
- Delayed deployments
- Inability to create organisations, applications and add-ons
We are currently experiencing an issue affecting some features of the Console, primarily related to metrics. Our team is actively working to resolve this problem. We will provide further updates as we progress.
The Git repository service for applications in our Montreal (MTL) region experienced an outage starting at 18:30 UTC on August 14, 2026. This issue went undetected by our monitoring systems. The problem has now been resolved. During the outage, git push operations and deployments without cache were affected.
The monitoring has detected that an hypervisor is unreachable on RBXHDS since 14:18 UTC. We are investigating. Add-ons and services hosted on this node are currently unreachable.
Preliminary inspection seems to lead to a network issue in the datacenter
We are currently experiencing an issue where access logs are not being properly computed into metrics for the Console. Our team is actively working to resolve this problem.
We are currently experiencing issues with the metrics page in the Console. Users are unable to generate metrics tokens or view metrics graphs. Our team is working to resolve this issue as quickly as possible. We will provide an update within the next 30 minutes.
Title: Infrastructure issue affecting Roubaix (RBX) region
Status: Identified
Body: We have identified an infrastructure issue in our Roubaix (RBX) region that may affect the availability and performance of services hosted there. Our team is working to resolve the issue as quickly as possible. For more details, please refer to the OVHcloud status page. We will provide further updates as the situation develops.
July 2026
We are currently observing slower than usual deployments across all regions. Some deployments may take significantly longer to complete, and in some cases the requested resources may fail to start.
Our team is investigating the issue. We will post an update as soon as we have more information.
A hypervisor in the PAR zone has become unavailable. This may impact the applications and services hosted on this node and result in service degradation or outages. The technical teams are currently investigating the root cause and working to restore the service as quickly as possible.
Deployments are currently experiencing degraded performance. Our teams are actively working to restore normal service. We’ll keep you updated as the situation evolves.
We have detected the loss of a network link between two of our availability zones (AZ) in Paris.
Impact: our infrastructure has sufficient redundancy to absorb this loss. No service disruption has been observed so far.
Current actions: our teams are working with our providers to identify the cause and restore the link.
We will update this incident as soon as we have more information.
We lost connection to the gov region.
We are looking for the source of the problem.
A maintenance operation is currently in progress on the Ceph infrastructure in par9, including the addition of new nodes to the cluster.
During this operation, part of the Ceph stack became unstable, which may have caused intermittent errors on Cellar / object storage access, including 503 responses observed by monitoring.
Active changes have been paused while the team investigates why some components are going down and coming back online. The cluster remains under close monitoring until it returns to a nominal state.
We are currently investigating an issue causing degraded performance on the Console and API. We will provide updates as more information becomes available.
We are currently investigating intermittent HTTP 503 errors on the Cellar S3 service in the Paris region. Some requests may fail randomly. We are actively working to identify the root cause and will post updates as soon as we have more information.
San storage of one of our hypervisor from our provider is inaccessible (see https://status.cloud-temple.com/incidents/wtjw3tbk5v14 ). After investigation with their support team and lack of estimated time for résolution we have decided to restore last backups of concerned data bases.
Restored databases are marked [RESTORED] and they have lost approximately 24 hours of data (last backups date from 2026-07-01 early morning). ~~Previous databases are still visible and marked as [INCIDENT] to anticipate the resolution of storage availability, which may give back access to their data (in which case a manual reconciliation would be possible).~~
EDIT 8:10 CEST : San storage is available again. Original databases are accessible again, and we have switched linked applications back on the databases. We remove the label [INCIDENT] as databases are no longer impacted, and we modify the label [RESTORE] to [2026-07-02_TEMP_RESTORE] . Those last databases are switched to read only mode , and can be used for verification that no data has been lost.
Please contact support of you require specific help
June 2026
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.
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.