Qovery had 9 outages in the last 2 years totaling 15h 36m of downtime — averaging 0.4 incidents per month.
There were 9 Qovery outages since April 27, 2026 totaling 15h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this incident.
This incident has been resolved.
All deployment jobs are currently stuck in the queue. We’re continuing to work on a fix for this incident.
We’ve identified the issue. Everything is running smoothly now, and we’ll continue monitoring the situation. You can restart your stuck deployments.
This incident has been resolved.
Type: Maintenance Affected Components: Customer infratructure, Infrastructure deployment Jun 15, 07:00:00 GMT+0 - Completed - As shared in [this post](https://www.qovery.com/changelog/qovery-managed-kubernetes-cluster-upgrade---moving-to-1-34-1-35), we will start upgrading some of your Kubernetes clusters to the new version. This week, we will start by upgrading all your **PRODUCTION** clusters. We do not yet have a precise time when we will trigger the update, but we will keep you informed as soon as we have more visibility
Type: Incident Affected Components: Terraform provider Jun 3, 15:18:17 GMT+0 - Postmortem - Jun 2, 20:44:33 GMT+0 - Resolved - This incident has been resolved. Jun 2, 15:00:00 GMT+0 - Resolved - This incident has been resolved. Our terraform provider was returning `unexpected error: 415 Unsupported Media Type - Could not parse Content-Type.` due to an incompatibility change on our reverse-proxy with our go qovery client sdk. We have rollbacked our change on the reverse proxy while we fix the issue in the client sdk.
Type: Maintenance Affected Components: Customer infratructure, Infrastructure deployment Jun 1, 07:00:00 GMT+0 - Completed - As shared in [this post](https://www.qovery.com/changelog/qovery-managed-kubernetes-cluster-upgrade---moving-to-1-34-1-35), we will start upgrading some of your Kubernetes clusters to the new version. This week, we will start by upgrading all your **NON-PRODUCTION** clusters. We do not yet have a precise time when we will trigger the update, but we will keep you informed as soon as we have more visibility
The console is currently reported as down. We found the issue and are rolling back the failed change now.
This incident has been resolved.
We are continuing to work on a fix for this incident.
We implemented a fix and are currently monitoring the result.
This incident has been resolved.
We are currently investigating this incident.
Type: Maintenance Affected Components: Customer infratructure, Infrastructure deployment May 11, 07:00:00 GMT+0 - Completed - As shared in [this post](https://www.qovery.com/changelog/qovery-managed-kubernetes-cluster-upgrade---moving-to-1-34-1-35), we will start upgrading some of your Kubernetes clusters to the new version. This week, we will start by upgrading all your **PRODUCTION** clusters. We do not yet have a precise time when we will trigger the update, but we will keep you informed as soon as we have more visibility
Type: Maintenance Affected Components: Customer infratructure, Infrastructure deployment Apr 27, 07:00:00 GMT+0 - Completed - As shared in [this post](https://www.qovery.com/changelog/qovery-managed-kubernetes-cluster-upgrade---moving-to-1-34-1-35), we will start upgrading some of your Kubernetes clusters to the new version. This week, we will start by upgrading all your **NON-PRODUCTION** clusters. We do not yet have a precise time when we will trigger the update, but we will keep you informed as soon as we have more visibility