Is Clever Cloud down?
French PaaS for applications and managed databases.
Uptime over 90 days
Incident history
Resolved: Github deployment disruption
Github deployments are working again
Resolved: An hypervisor is currently unreachable
After a period of monitoring, we consider this incident fully resolved
Resolved: Github deployment disruption
Some deployments were currently failing on the affected regions. We investigated the issue and rolled back the component update that caused it. It was always possible to start a successful deployment from the console or the cli. Not from a push on github for the duration of the incident.
Completed: Security upgrade on network components
We will be performing scheduled maintenance on core network equipment in Paris. The total time of operation will be around 4 hours. ### Expected Impact **No service disruption is expected.** The affected equipment will be decommissioned prior to the maintenance window, and network redundancy will remain fully operational throughout the process. This maintenance is part of a security update to
Monitoring: An hypervisor is currently unreachable
The hypervisor has been repaired and is back online. All affected services have recovered and impacted applications have been redeployed. This incident is now resolved.
Investigating: An hypervisor is currently unreachable
We are continuing to investigate an ongoing incident affecting services in our Paris region. A hardware failure on a hypervisor has been identified as the root cause. We are actively working to restore full service and will provide an update within the next 30 minutes.
Resolved: An hypervisor is currently unreachable
The monitoring has detected that an hypervisor is unreachable on Paris since 10 minutes. We are investigating. Add-ons and services hosted on this node are currently unreachable.
Resolved: Network issue on a single hypervisor in Paris region
One hypervisor in the Paris region experienced a brief issue between 12:20:09 UTC and 12:21:41 UTC. During this time, services hosted on it experienced both inbound and outbound network connectivity issues. Users might have encountered errors such as "TTL exceeded" or "Host is unreachable." The issue is now resolved.
Monitoring: Investigating issues with load balancers
All load balancers have been successfully restarted and are now operational. Service accessibility should be fully restored. We will continue to monitor the situation to ensure stability.
Identified: Investigating issues with load balancers
Our team is currently restarting the affected load balancers. Service accessibility should gradually return as this process completes. We will continue to monitor the situation and provide further updates as needed.
Investigating: Investigating issues with load balancers
We have determined that the issue is not related to the network but rather to our load balancing software (Sōzu). Our team is continuing to investigate the root cause. We will provide an update within the next 30 minutes.
Resolved: Investigating issues with load balancers
We are currently investigating issues affecting our load balancers. This may impact the availability and performance of applications hosted on our platform. Our team is working to identify the root cause. We will provide an update within the next 30 minutes.
Resolved: Access logs access and metrics issues
System has fully recovered.
Resolved: Investigation into email and webhook notification delays
The issue has been identified and resolved. Notifications should now be functioning normally. Our team continues to monitor the situation closely.
Resolved: Investigation into email and webhook notification delays
We are currently investigating delays in sending email and webhook notifications. Some users may experience a delay in receiving these notifications. Our team is actively working to identify the root cause. We will provide an update within the next 30 minutes.
Resolved: Deployments experiencing issues
The issue with build cache has been resolved. Deployments should now proceed correctly. Customers who modified their configurations to work around this issue can revert to their original settings.
Identified: Deployments experiencing issues
The issue affecting deployment statuses in the web console has been resolved. However, deployments using build cache (on Pico / Nano instances, or dedicated build instances) are still failing and building on the runtime instance instead, which may cause delays or failures. Customers experiencing these issues can disable the dedicated build instance (application's information -> uncheck "disable d
Identified: Deployments experiencing issues
We have identified the issue affecting deployments statuses in the web console and deployments using build cache on Pico / Nano instances or dedicated build instances. Customers experiencing deployment failures or delays due to missing build cache feature are advised to disable dedicated build instance (application's informations -> uncheck "disable dedicated build instance") and use an instance
Investigating: Deployments experiencing issues
We are also aware of an issue where deployments using build cache (on Pico / Nano instances, or dedicated build instances) are failing and instead building on the runtime instance. This may cause delays in application deployments and / or deployment failures. Our team is actively working to identify the root cause and resolve the issue. We will provide an update within the next 30 minutes.
Resolved: Deployments experiencing issues
We are currently experiencing issues with deployment statuses. Applications that are already running are unaffected. Our team is investigating the problem. We will provide an update within the next 30 minutes.
Monitoring: Access logs access and metrics issues
System is recovering from the backlog of access logs to ingest.
Resolved: Access logs access and metrics issues
We are seeing data pipelines failing to compute properly access logs since 08:09 (UTC), we are working on resolution. Access logs are not lost, they will be re-computed and catch-up again once the incident is fixed.
Resolved: NetworkGroups service degradation
Our systems have fully recovered from the recent network-related issues. We will continue to monitor the situation to ensure ongoing stability.
Monitoring: NetworkGroups service degradation
Our systems are recovering from the recent network-related issues. We continue to monitor the situation closely to ensure stability. We will provide another update if necessary.
Resolved: NetworkGroups service degradation
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.
Official source
Everything on this page comes from Clever Cloud's public status page, and nowhere else.
Official status pageOther cloud & infrastructure services
Frequently asked questions
Is Clever Cloud down right now?
As of the last check (2026-09-14 08:10 UTC), Clever Cloud reports “Operational” on its official status page. 7 ongoing incidents, latest: Investigating: An hypervisor is currently unreachable.
What is Clever Cloud's uptime over the last 90 days?
Clever Cloud shows 100.00% uptime over the last 90 days, across 41 published incident(s).
How do I get notified automatically when Clever Cloud goes down?
Create a free alert on StatusPulse: as soon as an incident is published on Clever Cloud's status page, you get an email (or a Slack/webhook notification on a paid plan).