Qovery Outage History

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

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