Qovery Outage History

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

This incident has been resolved.

This incident has been resolved.

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

Type: Maintenance Duration: 1 day, 7 hours and 32 minutes Affected Components: Customer infratructure Oct 6, 07:00:00 GMT+0 - Identified - As shared in [this post](https://discuss.qovery.com/t/important-qovery-managed-kubernetes-cluster-upgrade-moving-to-1-32-1-33/6822), 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 Oct 7, 14:32:09 GMT+0 - Completed - Maintenance has completed successfully.

Type: Maintenance Duration: 6 hours and 10 minutes Affected Components: Customer infratructure Sep 22, 07:00:00 GMT+0 - Identified - As shared in [this post](https://discuss.qovery.com/t/important-qovery-managed-kubernetes-cluster-upgrade-moving-to-1-32-1-33/6822), 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 Sep 22, 13:09:31 GMT+0 - Completed - All non-production clusters have been updated to Kubernetes 1.33 Sep 22, 07:00:01 GMT+0 - Identified - Maintenance is now in progress

Type: Maintenance Duration: 1 day, 5 hours and 7 minutes Affected Components: Customer infratructure Sep 8, 07:00:00 GMT+0 - Identified - As shared in [this post](https://discuss.qovery.com/t/important-qovery-managed-kubernetes-cluster-upgrade-moving-to-1-32-1-33/6822), 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 Sep 8, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 9, 12:06:52 GMT+0 - Completed - Maintenance has completed successfully.

Type: Incident Duration: 4 hours Affected Components: AWS Sep 1, 18:56:52 GMT+0 - Resolved - This incident has been resolved. Sep 1, 14:56:29 GMT+0 - Identified - Please refer to[ this document](https://docs.google.com/document/d/1JyniDDBtwiPOzk31pnMqdUIH-6z77L1HC-8LBEbThzg/edit?usp=sharing) for remediation. We are currently investigating this incident.

Type: Maintenance Duration: 3 hours and 36 minutes Affected Components: Customer infratructure Aug 25, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 25, 10:36:22 GMT+0 - Completed - Maintenance has completed successfully. Aug 25, 07:00:00 GMT+0 - Identified - As shared in [this post](https://discuss.qovery.com/t/important-qovery-managed-kubernetes-cluster-upgrade-moving-to-1-32-1-33/6822), 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

Type: Incident Duration: 4 hours and 6 minutes Jul 22, 08:59:23 GMT+0 - Identified - Our 3rd party solution to manage certificates creation and renewal (Let's encrypt) is having issues with the certificate generation. We are monitoring the situation with our partner. Jul 22, 13:05:31 GMT+0 - Resolved - The incident has been solved by let's encrypt. Certificate generation and renewal is back to normal

Type: Incident Duration: 40 minutes Affected Components: Api Jun 6, 17:40:00 GMT+0 - Investigating - We are currently investigating this incident. Jun 6, 18:20:00 GMT+0 - Resolved - This incident has been resolved.

Type: Incident Duration: 3 hours and 20 minutes Affected Components: Api Jun 5, 18:20:00 GMT+0 - Resolved - This incident has been resolved. Jun 5, 17:40:00 GMT+0 - Investigating - We are currently investigating this incident.

Type: Incident Duration: 5 hours and 14 minutes Affected Components: Infrastructure deployment May 26, 13:11:11 GMT+0 - Investigating - We are currently investigating this incident. May 26, 13:28:26 GMT+0 - Identified - We are continuing to work on a fix for this incident. May 26, 18:25:35 GMT+0 - Resolved - This incident has been resolved.

Type: Incident Duration: 1 hour and 38 minutes Affected Components: Environment deployment Apr 8, 16:07:14 GMT+0 - Investigating - The auto-deploy feature doesn't work from time to time when a push / merge is executed on the repository of your applications. We are currently investigating this incident. In the meantime, please check that your applications are properly deployed Apr 8, 16:33:26 GMT+0 - Identified - The issue is present only on GitHub and it is due to a recent change in the payload sent by Github We are working on a fix Apr 8, 17:45:13 GMT+0 - Resolved - We have released the fix. Any commits on github pushed before this update have not been deployed automatically, and you should deploy them manually (or wait for the next commit) This incident has been resolved.

Type: Maintenance Duration: 1 day and 38 minutes Affected Components: Infrastructure deployment, Customer infratructure Mar 10, 08:01:01 GMT+0 - Identified - Maintenance is now in progress Mar 11, 08:39:13 GMT+0 - Completed - The cluster upgrade has been completed the 10/03! Mar 10, 08:01:00 GMT+0 - Identified - As shared in [this post](https://discuss.qovery.com/t/important-qovery-managed-kubernetes-cluster-upgrade-moving-to-1-31/6815), 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 have yet a precise time when we will trigger the update, we will keep you informed as soon as we have more visibility

Type: Incident Duration: 58 minutes Affected Components: Console Mar 3, 14:45:43 GMT+0 - Identified - We have found the fix and re-deploying all the clusters Mar 3, 14:14:43 GMT+0 - Investigating - * the environment and services are displayed in the console as "stopped" while the environments run properly. There's no impact on your environments, you can continue to deploy your applications with no risk. * SSH and port-forward features are not working anymore We are currently investigating this incident. Mar 3, 15:10:32 GMT+0 - Monitoring - A fix has been deployed. It is possible you have to clear the browser cache (Ctrl + Shift + R) to see the statuses again. Mar 3, 15:12:17 GMT+0 - Resolved - A fix has been deployed. It is possible you have to clear the browser cache (Ctrl + Shift + R) to see the statuses again.

Type: Maintenance Duration: 2 days and 21 minutes Affected Components: Infrastructure deployment, Customer infratructure Mar 5, 08:20:31 GMT+0 - Completed - Maintenance has completed successfully. Mar 3, 08:00:00 GMT+0 - Identified - As shared in [this post](https://discuss.qovery.com/t/important-qovery-managed-kubernetes-cluster-upgrade-moving-to-1-31/6815), 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 have yet a precise time when we will trigger the update, we will keep you informed as soon as we have more visibility Mar 3, 08:00:01 GMT+0 - Identified - Maintenance is now in progress

Type: Incident Duration: 2 hours and 3 minutes Affected Components: Environment deployment Jan 28, 18:31:18 GMT+0 - Resolved - The issue is finally closed but the root cause has not been identified (probably external) Jan 28, 17:16:56 GMT+0 - Monitoring - The issue seems to have disappeared, we are trying to understand why Jan 28, 16:28:29 GMT+0 - Investigating - Container deployment is experiencing issues during the Mirroring step (long mirroring potentially failing) We are investigating

Type: Incident Duration: 2 hours and 34 minutes Nov 12, 13:00:00 GMT+0 - Identified - Following the latest release of PostgreSQL Bitnami Image, there is a missing variable when starting the DB. Official issue: [Here](https://github.com/bitnami/containers/issues/74804) and [Here](https://github.com/bitnami/charts/issues/30415) We are continuing to work on a fix for this incident. In the meantime, please do not redeploy your ContainerDB. Nov 12, 15:34:13 GMT+0 - Resolved - We published a fix with the needed environment variables. We are waiting for the official Bitnami's fix. If you encounter any error, please redeploy your ContainerDB. This incident is resolved.

Type: Incident Affected Components: Environment deployment Oct 22, 03:00:00 GMT+0 - Resolved - Most deployment failed with timeout. This incident has been resolved.