Qovery Status - Incident history https://status.qovery.com Qovery Thu, 8 Oct 2026 10:50:03 +0000 Console unreachable and authentication issues through the CLI Type: Incident Duration: 1 hour and 45 minutes Affected Components: Emails, Api, Customer infratructure, Environment deployment, Console, Infrastructure deployment, Terraform provider Oct 8, 12:34:43 GMT+0 - Resolved - This incident has been resolved. Oct 8, 10:57:54 GMT+0 - Monitoring - The situation has been stabilized and the team is keeping an eye on it. Some clusters deployments may appear as failed, our team is currently working on updating them properly, the clusters themselves are fine, it is just the report of their latest deployment which is impacted. Oct 8, 10:50:03 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 1 hour and 45 minutes

Affected Components: , , , , , ,

Oct 8, 12:34:43 GMT+0
Resolved - This incident has been resolved..

Oct 8, 10:57:54 GMT+0
Monitoring - The situation has been stabilized and the team is keeping an eye on it. Some clusters deployments may appear as failed, our team is currently working on updating them properly, the clusters themselves are fine, it is just the report of their latest deployment which is impacted..

Oct 8, 10:50:03 GMT+0
Investigating - We are currently investigating this incident..

]]> Thu, 8 Oct 2026 10:50:03 +0000 https://status.qovery.com/incident/cmuzf0aoh02ex0wmy15fyr026 https://status.qovery.com/incident/cmuzf0aoh02ex0wmy15fyr026 Console access and CLI authentication issues Type: Incident Duration: 42 minutes Affected Components: Emails, Api, Customer infratructure, Environment deployment, Console, Infrastructure deployment, Terraform provider Oct 8, 09:42:13 GMT+0 - Resolved - This incident has been resolved. Oct 8, 09:36:20 GMT+0 - Monitoring - We've deployed a fix for this incident. The console and CLI are now available again. The still is still monitoring the situation. Oct 8, 09:10:00 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 42 minutes

Affected Components: , , , , , ,

Oct 8, 09:42:13 GMT+0
Resolved - This incident has been resolved..

Oct 8, 09:36:20 GMT+0
Monitoring - We've deployed a fix for this incident. The console and CLI are now available again. The still is still monitoring the situation..

Oct 8, 09:10:00 GMT+0
Investigating - We are currently investigating this incident..

]]> Thu, 8 Oct 2026 09:10:00 +0000 https://status.qovery.com/incident/cmuzbvl8e00re14lamvw2rubj https://status.qovery.com/incident/cmuzbvl8e00re14lamvw2rubj All deployment jobs are currently stuck in the queue Type: Incident Duration: 14 hours and 46 minutes Affected Components: Environment deployment, Infrastructure deployment Jul 21, 10:18:51 GMT+0 - Postmortem - <https://docs.google.com/document/d/1VRsljfgoe3c2E7l%5FrkueYI1HC81UlLWriM7RWEv6HfA/edit?tab=t.0> Jul 21, 07:46:27 GMT+0 - Resolved - This incident has been resolved. Jul 20, 18:33:21 GMT+0 - Monitoring - We’ve identified the issue. Everything is running smoothly now, and we’ll continue monitoring the situation. You can restart your stuck deployments. Jul 20, 17:00:22 GMT+0 - Investigating - All deployment jobs are currently stuck in the queue. We’re continuing to work on a fix for this incident. Type: Incident

Duration: 14 hours and 46 minutes

Affected Components: ,

Jul 21, 10:18:51 GMT+0
Postmortem - <https://docs.google.com/document/d/1VRsljfgoe3c2E7l%5FrkueYI1HC81UlLWriM7RWEv6HfA/edit?tab=t.0>.

Jul 21, 07:46:27 GMT+0
Resolved - This incident has been resolved..

Jul 20, 18:33:21 GMT+0
Monitoring - We’ve identified the issue. Everything is running smoothly now, and we’ll continue monitoring the situation. You can restart your stuck deployments. .

Jul 20, 17:00:22 GMT+0
Investigating - All deployment jobs are currently stuck in the queue. We’re continuing to work on a fix for this incident..

]]> Mon, 20 Jul 2026 17:00:22 +0000 https://status.qovery.com/incident/cmrtjdxbs008k0ro836egttzy https://status.qovery.com/incident/cmrtjdxbs008k0ro836egttzy Kubernetes upgrade 1.35 - PRODUCTION clusters 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: Maintenance

Affected Components: ,

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.

]]> Mon, 15 Jun 2026 07:00:00 +0000 https://status.qovery.com/maintenance/cmnpswj4i00damhf3qeyrnij1 https://status.qovery.com/maintenance/cmnpswj4i00damhf3qeyrnij1 Terraform provider Type: Incident Affected Components: Terraform provider Jun 3, 15:18:17 GMT+0 - Postmortem - <https://docs.google.com/document/d/1da39qYBRlHI7orjzWxZmYkTYAh7G22aMxye8s0UbFcE/edit?usp=sharing> 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: Incident

Affected Components:

Jun 3, 15:18:17 GMT+0
Postmortem - <https://docs.google.com/document/d/1da39qYBRlHI7orjzWxZmYkTYAh7G22aMxye8s0UbFcE/edit?usp=sharing>.

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..

]]> Tue, 2 Jun 2026 15:00:00 +0000 https://status.qovery.com/incident/cmpx52xlc00einwp9ivn5qb9d https://status.qovery.com/incident/cmpx52xlc00einwp9ivn5qb9d Kubernetes upgrade 1.35 - NON-PRODUCTION clusters 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 Type: Maintenance

Affected Components: ,

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.

]]> Mon, 1 Jun 2026 07:00:00 +0000 https://status.qovery.com/maintenance/cmnpsvgqp00s3b6jkrvw95mzv https://status.qovery.com/maintenance/cmnpsvgqp00s3b6jkrvw95mzv Console down Type: Incident Duration: 15 minutes Affected Components: Console May 22, 14:02:44 GMT+0 - Resolved - This incident has been resolved. May 22, 14:02:31 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. May 22, 13:57:08 GMT+0 - Identified - We are continuing to work on a fix for this incident. May 22, 13:53:23 GMT+0 - Resolved - This incident has been resolved. May 22, 13:47:16 GMT+0 - Identified - The console is currently reported as down. We found the issue and are rolling back the failed change now. Type: Incident

Duration: 15 minutes

Affected Components:

May 22, 14:02:44 GMT+0
Resolved - This incident has been resolved..

May 22, 14:02:31 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

May 22, 13:57:08 GMT+0
Identified - We are continuing to work on a fix for this incident..

May 22, 13:53:23 GMT+0
Resolved - This incident has been resolved..

May 22, 13:47:16 GMT+0
Identified - The console is currently reported as down. We found the issue and are rolling back the failed change now..

]]> Fri, 22 May 2026 13:47:16 +0000 https://status.qovery.com/incident/cmpgz4tu2005sqh39llu7rirz https://status.qovery.com/incident/cmpgz4tu2005sqh39llu7rirz Kubernetes upgrade 1.34 - PRODUCTION clusters 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: ,

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.

]]> Mon, 11 May 2026 07:00:00 +0000 https://status.qovery.com/maintenance/cmnpsu53700pa14mjvw5g7ytz https://status.qovery.com/maintenance/cmnpsu53700pa14mjvw5g7ytz Qovery scheduled maintenance Type: Maintenance Duration: 5 minutes Affected Components: Environment deployment, Infrastructure deployment, Api, Console May 4, 07:05:00 GMT+0 - Completed - Maintenance has completed successfully May 4, 07:00:01 GMT+0 - Identified - Maintenance is now in progress May 4, 07:00:00 GMT+0 - Identified - To upgrade databases with security patches that require downtime. Qovery will be unavailable for a few minutes. Only Qovery services are impacted, your services running on your infrastructure is staying available Type: Maintenance

Duration: 5 minutes

Affected Components: , , ,

May 4, 07:05:00 GMT+0
Completed - Maintenance has completed successfully.

May 4, 07:00:01 GMT+0
Identified - Maintenance is now in progress.

May 4, 07:00:00 GMT+0
Identified - To upgrade databases with security patches that require downtime. Qovery will be unavailable for a few minutes. Only Qovery services are impacted, your services running on your infrastructure is staying available.

]]> Mon, 4 May 2026 07:00:00 +0000 https://status.qovery.com/maintenance/cmoli65xi083kuzqetap466ej https://status.qovery.com/maintenance/cmoli65xi083kuzqetap466ej Kubernetes upgrade 1.34 - NON-PRODUCTION clusters 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

Affected Components: ,

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.

]]> Mon, 27 Apr 2026 07:00:00 +0000 https://status.qovery.com/maintenance/cmnpssil6000xxnamtznl80nl https://status.qovery.com/maintenance/cmnpssil6000xxnamtznl80nl Kubernetes upgrade 1.33 - PRODUCTION clusters Type: Maintenance Duration: 1 day, 7 hours and 32 minutes Affected Components: Customer infratructure Oct 7, 14:32:09 GMT+0 - Completed - Maintenance has completed successfully. 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 Type: Maintenance

Duration: 1 day, 7 hours and 32 minutes

Affected Components:

Oct 7, 14:32:09 GMT+0
Completed - Maintenance has completed successfully..

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.

]]> Mon, 6 Oct 2025 07:00:00 +0000 https://status.qovery.com/maintenance/cmdo4tm9j01okc4m7jwvo3e23 https://status.qovery.com/maintenance/cmdo4tm9j01okc4m7jwvo3e23 Kubernetes upgrade 1.33 - NON-PRODUCTION clusters Type: Maintenance Duration: 6 hours and 10 minutes Affected Components: Customer infratructure 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 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 Type: Maintenance

Duration: 6 hours and 10 minutes

Affected Components:

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.

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.

]]> Mon, 22 Sep 2025 07:00:00 +0000 https://status.qovery.com/maintenance/cmdo4s54n008gha3rmzz4t6d7 https://status.qovery.com/maintenance/cmdo4s54n008gha3rmzz4t6d7 Kubernetes upgrade 1.32 - PRODUCTION clusters Type: Maintenance Duration: 1 day, 5 hours and 7 minutes Affected Components: Customer infratructure Sep 9, 12:06:52 GMT+0 - Completed - Maintenance has completed successfully. Sep 8, 07:00:01 GMT+0 - Identified - Maintenance is now in progress 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 Type: Maintenance

Duration: 1 day, 5 hours and 7 minutes

Affected Components:

Sep 9, 12:06:52 GMT+0
Completed - Maintenance has completed successfully..

Sep 8, 07:00:01 GMT+0
Identified - Maintenance is now in progress.

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.

]]> Mon, 8 Sep 2025 07:00:00 +0000 https://status.qovery.com/maintenance/cmdo4qs730036r1whdrm1nuz2 https://status.qovery.com/maintenance/cmdo4qs730036r1whdrm1nuz2 Qovery maintenance Type: Maintenance Duration: 52 minutes Affected Components: Environment deployment, Api, Console, Infrastructure deployment Sep 8, 06:52:19 GMT+0 - Completed - Maintenance has completed successfully. Sep 8, 06:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 8, 06:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Type: Maintenance

Duration: 52 minutes

Affected Components: , , ,

Sep 8, 06:52:19 GMT+0
Completed - Maintenance has completed successfully..

Sep 8, 06:00:01 GMT+0
Identified - Maintenance is now in progress.

Sep 8, 06:00:00 GMT+0
Identified - We are planning for a scheduled maintenance during that time..

]]> Mon, 8 Sep 2025 06:00:00 +0000 https://status.qovery.com/maintenance/cmevcv45m000nzl1n9fme8xwq https://status.qovery.com/maintenance/cmevcv45m000nzl1n9fme8xwq [AWS ONLY] Deployments failing due to IAM trust policy change 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: Incident

Duration: 4 hours

Affected Components:

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. .

]]> Mon, 1 Sep 2025 14:56:29 +0000 https://status.qovery.com/incident/cmf18sr8q000cxozldaizj8nu https://status.qovery.com/incident/cmf18sr8q000cxozldaizj8nu Kubernetes upgrade 1.32 - NON-PRODUCTION clusters Type: Maintenance Duration: 3 hours and 36 minutes Affected Components: Customer infratructure Aug 25, 10:36:22 GMT+0 - Completed - Maintenance has completed successfully. Aug 25, 07:00:01 GMT+0 - Identified - Maintenance is now in progress 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: Maintenance

Duration: 3 hours and 36 minutes

Affected Components:

Aug 25, 10:36:22 GMT+0
Completed - Maintenance has completed successfully..

Aug 25, 07:00:01 GMT+0
Identified - Maintenance is now in progress.

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.

]]> Mon, 25 Aug 2025 07:00:00 +0000 https://status.qovery.com/maintenance/cmdo4o5or01nuc4m7i8c3kivp https://status.qovery.com/maintenance/cmdo4o5or01nuc4m7i8c3kivp TLS Certificate creation/renewal impacted for your application - Ongoing issue with Let's encrypt Type: Incident Duration: 4 hours and 6 minutes 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 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. Type: Incident

Duration: 4 hours and 6 minutes

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.

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..

]]> Tue, 22 Jul 2025 08:59:23 +0000 https://status.qovery.com/incident/cmdeazlix00o5sb5utjt540yj https://status.qovery.com/incident/cmdeazlix00o5sb5utjt540yj API TLS issue Type: Incident Duration: 40 minutes Affected Components: Api Jun 6, 18:20:00 GMT+0 - Resolved - This incident has been resolved. Jun 6, 17:40:00 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 40 minutes

Affected Components:

Jun 6, 18:20:00 GMT+0
Resolved - This incident has been resolved..

Jun 6, 17:40:00 GMT+0
Investigating - We are currently investigating this incident..

]]> Fri, 6 Jun 2025 17:40:00 +0000 https://status.qovery.com/incident/cmbla7y6r001eig8avbny56vn https://status.qovery.com/incident/cmbla7y6r001eig8avbny56vn TLS issue on Qovery API 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: 3 hours and 20 minutes

Affected Components:

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..

]]> Thu, 5 Jun 2025 17:40:00 +0000 https://status.qovery.com/incident/cmbl9w5jc002i8p9jvdhxxw5w https://status.qovery.com/incident/cmbl9w5jc002i8p9jvdhxxw5w Scaleway non-production cluster deployment issue. Type: Incident Duration: 5 hours and 14 minutes Affected Components: Infrastructure deployment May 26, 18:25:35 GMT+0 - Resolved - This incident has been resolved. May 26, 13:28:26 GMT+0 - Identified - We are continuing to work on a fix for this incident. May 26, 13:11:11 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 5 hours and 14 minutes

Affected Components:

May 26, 18:25:35 GMT+0
Resolved - This incident has been resolved..

May 26, 13:28:26 GMT+0
Identified - We are continuing to work on a fix for this incident..

May 26, 13:11:11 GMT+0
Investigating - We are currently investigating this incident..

]]> Mon, 26 May 2025 13:11:11 +0000 https://status.qovery.com/incident/cmb53vwzq006kpep756q8zzz7 https://status.qovery.com/incident/cmb53vwzq006kpep756q8zzz7 Qovery maintenance Type: Maintenance Duration: 3 hours and 38 minutes Affected Components: Api, Emails, Console, Infrastructure deployment, Environment deployment, Customer infratructure Apr 14, 11:35:59 GMT+0 - Completed - maintenance completed! Apr 14, 09:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. <https://discuss.qovery.com/t/important-qovery-maintenance-03-17-2024-from-9am-to-11am-paris-time/6818> Apr 14, 08:00:00 GMT+0 - Identified - Maintenance rescheduled to the 04/14/2025 Apr 14, 07:58:26 GMT+0 - Identified - Maintenance has started. You might experience some failure while connecting to our console, using our CLI/Terraform provider or connecting to our API. Some deployment requests might not be triggered We will write an update here when the upgrade is completed Type: Maintenance

Duration: 3 hours and 38 minutes

Affected Components: , , , , ,

Apr 14, 11:35:59 GMT+0
Completed - maintenance completed!.

Apr 14, 09:00:00 GMT+0
Identified - We are planning for a scheduled maintenance during that time. <https://discuss.qovery.com/t/important-qovery-maintenance-03-17-2024-from-9am-to-11am-paris-time/6818>.

Apr 14, 08:00:00 GMT+0
Identified - Maintenance rescheduled to the 04/14/2025.

Apr 14, 07:58:26 GMT+0
Identified - Maintenance has started. You might experience some failure while connecting to our console, using our CLI/Terraform provider or connecting to our API. Some deployment requests might not be triggered We will write an update here when the upgrade is completed.

]]> Mon, 14 Apr 2025 08:00:00 +0000 https://status.qovery.com/maintenance/cm84dd6oj002jfy6bwzy01mco https://status.qovery.com/maintenance/cm84dd6oj002jfy6bwzy01mco Application Auto-deploy not working on GitHub Type: Incident Duration: 1 hour and 38 minutes Affected Components: Environment deployment 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. 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 <https://github.blog/changelog/> We are working on a fix 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 Type: Incident

Duration: 1 hour and 38 minutes

Affected Components:

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..

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 <https://github.blog/changelog/> We are working on a fix.

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.

]]> Tue, 8 Apr 2025 16:07:14 +0000 https://status.qovery.com/incident/cm98p1dgi000sszh9jxd0anac https://status.qovery.com/incident/cm98p1dgi000sszh9jxd0anac Kubernetes upgrade 1.31 - PRODUCTION clusters Type: Maintenance Duration: 1 day and 38 minutes Affected Components: Infrastructure deployment, Customer infratructure Mar 11, 08:39:13 GMT+0 - Completed - The cluster upgrade has been completed the 10/03! Mar 10, 08:01:01 GMT+0 - Identified - Maintenance is now in progress 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: Maintenance

Duration: 1 day and 38 minutes

Affected Components: ,

Mar 11, 08:39:13 GMT+0
Completed - The cluster upgrade has been completed the 10/03! .

Mar 10, 08:01:01 GMT+0
Identified - Maintenance is now in progress.

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.

]]> Mon, 10 Mar 2025 08:01:00 +0000 https://status.qovery.com/maintenance/cm7bos93l000do0hlgk7u41m5 https://status.qovery.com/maintenance/cm7bos93l000do0hlgk7u41m5 environment/services displayed as "stopped" + SSH/port-forward not working Type: Incident Duration: 58 minutes Affected Components: Console 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. 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, 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. Type: Incident

Duration: 58 minutes

Affected Components:

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..

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, 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..

]]> Mon, 3 Mar 2025 14:14:43 +0000 https://status.qovery.com/incident/cm7t560bt000yv93sfali3cy6 https://status.qovery.com/incident/cm7t560bt000yv93sfali3cy6 Kubernetes upgrade 1.31 - NON-PRODUCTION clusters 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:01 GMT+0 - Identified - Maintenance is now in progress 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 Type: Maintenance

Duration: 2 days and 21 minutes

Affected Components: ,

Mar 5, 08:20:31 GMT+0
Completed - Maintenance has completed successfully..

Mar 3, 08:00:01 GMT+0
Identified - Maintenance is now in progress.

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.

]]> Mon, 3 Mar 2025 08:00:00 +0000 https://status.qovery.com/maintenance/cm7booyfm000ghy5wm62rjidq https://status.qovery.com/maintenance/cm7booyfm000ghy5wm62rjidq Container deployment experiencing issues during the Mirroring step 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 3 minutes

Affected Components:

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.

]]> Tue, 28 Jan 2025 16:28:29 +0000 https://status.qovery.com/incident/cm6goz2l30001qswre7xrcahb https://status.qovery.com/incident/cm6goz2l30001qswre7xrcahb Qovery maintenance Type: Maintenance Duration: 3 hours and 22 minutes Affected Components: Api, Emails, Console, Infrastructure deployment, Environment deployment Nov 18, 11:45:58 GMT+0 - Completed - Maintenance has completed successfully. Nov 18, 08:24:14 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. <https://discuss.qovery.com/t/important-qovery-maintenance-11-18-2024-from-8am-to-10am-paris-time/3668> Type: Maintenance

Duration: 3 hours and 22 minutes

Affected Components: , , , ,

Nov 18, 11:45:58 GMT+0
Completed - Maintenance has completed successfully..

Nov 18, 08:24:14 GMT+0
Identified - We are planning for a scheduled maintenance during that time. <https://discuss.qovery.com/t/important-qovery-maintenance-11-18-2024-from-8am-to-10am-paris-time/3668> .

]]> Mon, 18 Nov 2024 08:24:14 +0000 https://status.qovery.com/maintenance/cm3mrgwxq00145juwo5l9sfze https://status.qovery.com/maintenance/cm3mrgwxq00145juwo5l9sfze Problem with PostgreSQL ContainerDB. Type: Incident Duration: 2 hours and 34 minutes 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. 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. Type: Incident

Duration: 2 hours and 34 minutes

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. .

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..

]]> Tue, 12 Nov 2024 13:00:00 +0000 https://status.qovery.com/incident/cm3ej64fw000piz38sa2o9w7g https://status.qovery.com/incident/cm3ej64fw000piz38sa2o9w7g Deployment Timeout Type: Incident Affected Components: Environment deployment Oct 22, 03:00:00 GMT+0 - Resolved - Most deployment failed with timeout. This incident has been resolved. Type: Incident

Affected Components:

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

]]> Tue, 22 Oct 2024 03:00:00 +0000 https://status.qovery.com/incident/cm2k6w4xw003kj5h2ixvaazb5 https://status.qovery.com/incident/cm2k6w4xw003kj5h2ixvaazb5 Standard Non-production cluster Update Type: Maintenance Duration: 4 hours Affected Components: Infrastructure deployment, Environment deployment Sep 16, 12:00:00 GMT+0 - Completed - Maintenance has completed successfully Sep 16, 08:00:00 GMT+0 - Identified - ### **Update - September 12, 2024** The scheduled update for **non-production clusters** did not take place today due to issues with our ARM image. To avoid any potential risks, we have decided to postpone the update. The issue has since been resolved, and we have rescheduled the maintenance to **September 16, 2024 at 8:00 AM UTC**. The update will be applied to your production clusters on **September 19, 2024, at 8:00 AM UTC.** However, if you choose to manually update your production cluster in Qovery before this date, the update will be automatically applied. Sep 16, 08:00:00 GMT+0 - Identified - ### **Cluster Updates on September 16, 2024, at 8:00 AM UTC** Please be aware that updates will be applied to your non-production clusters, and actions may be required in the future. Key changes: * **Cert-manager update**: [Read more](https://discuss.qovery.com/t/action-required-update-cert-manager-ingress-class/3343) * **NGINX Ingress name update**: [Read more](https://discuss.qovery.com/t/action-required-ingress-nginx-ingress-name-change/3350) * **ALB controller flag** will be enabled for non-production clusters only: [Read more](https://discuss.qovery.com/t/aws-migration-moving-from-nlb-controller-to-alb-controller/2953) The update will be applied to your production clusters on **September 19, 2024, at 8:00 AM UTC.** However, if you choose to manually update your production cluster in Qovery before this date, the update will be automatically applied. Type: Maintenance

Duration: 4 hours

Affected Components: ,

Sep 16, 12:00:00 GMT+0
Completed - Maintenance has completed successfully.

Sep 16, 08:00:00 GMT+0
Identified - ### **Update - September 12, 2024** The scheduled update for **non-production clusters** did not take place today due to issues with our ARM image. To avoid any potential risks, we have decided to postpone the update. The issue has since been resolved, and we have rescheduled the maintenance to **September 16, 2024 at 8:00 AM UTC**. The update will be applied to your production clusters on **September 19, 2024, at 8:00 AM UTC.** However, if you choose to manually update your production cluster in Qovery before this date, the update will be automatically applied..

Sep 16, 08:00:00 GMT+0
Identified - ### **Cluster Updates on September 16, 2024, at 8:00 AM UTC** Please be aware that updates will be applied to your non-production clusters, and actions may be required in the future. Key changes: * **Cert-manager update**: [Read more](https://discuss.qovery.com/t/action-required-update-cert-manager-ingress-class/3343) * **NGINX Ingress name update**: [Read more](https://discuss.qovery.com/t/action-required-ingress-nginx-ingress-name-change/3350) * **ALB controller flag** will be enabled for non-production clusters only: [Read more](https://discuss.qovery.com/t/aws-migration-moving-from-nlb-controller-to-alb-controller/2953) The update will be applied to your production clusters on **September 19, 2024, at 8:00 AM UTC.** However, if you choose to manually update your production cluster in Qovery before this date, the update will be automatically applied..

]]> Mon, 16 Sep 2024 08:00:00 +0000 https://status.qovery.com/maintenance/cm0y62q5q0006mbv4qaj70wtc https://status.qovery.com/maintenance/cm0y62q5q0006mbv4qaj70wtc 403 received Nginx customer side Type: Incident Duration: 3 hours and 17 minutes Affected Components: Customer infratructure Aug 30, 13:18:57 GMT+0 - Resolved - Following a global cluster update triggered by our team, some configuration of the Nginx Ingress controller was wrongly modified on a subset of these clusters. Our team identified the root cause of the problem and deployed a fix on all clusters. The websites hosted on impacted clusters were unreachable during the outage. You can find more information on [this forum thread](https://discuss.qovery.com/t/post-mortem-http-requests-failing-with-403/3065) We apologize for any inconvenience caused. Aug 28, 16:40:00 GMT+0 - Resolved - Our team has identified the root cause of this issue; however, further investigation is required, as the bug appears to have impacted configurations that should have remained unaffected. We are actively working to fully understand the scope and prevent any recurrence. We apologize for any inconvenience caused and appreciate your patience as we work to investigate this matter promptly. Aug 28, 14:00:00 GMT+0 - Identified - We want to inform you of a recent incident involving customers' Nginx configuration that affected some customers. Specifically, a conflicting setting was released that impacted customers with IP whitelists configured on their services, resulting in their requests being denied with an HTTP 403 error. Investigation is in progress Type: Incident

Duration: 3 hours and 17 minutes

Affected Components:

Aug 30, 13:18:57 GMT+0
Resolved - Following a global cluster update triggered by our team, some configuration of the Nginx Ingress controller was wrongly modified on a subset of these clusters. Our team identified the root cause of the problem and deployed a fix on all clusters. The websites hosted on impacted clusters were unreachable during the outage. You can find more information on [this forum thread](https://discuss.qovery.com/t/post-mortem-http-requests-failing-with-403/3065) We apologize for any inconvenience caused..

Aug 28, 16:40:00 GMT+0
Resolved - Our team has identified the root cause of this issue; however, further investigation is required, as the bug appears to have impacted configurations that should have remained unaffected. We are actively working to fully understand the scope and prevent any recurrence. We apologize for any inconvenience caused and appreciate your patience as we work to investigate this matter promptly..

Aug 28, 14:00:00 GMT+0
Identified - We want to inform you of a recent incident involving customers' Nginx configuration that affected some customers. Specifically, a conflicting setting was released that impacted customers with IP whitelists configured on their services, resulting in their requests being denied with an HTTP 403 error. Investigation is in progress.

]]> Wed, 28 Aug 2024 14:00:00 +0000 https://status.qovery.com/incident/cm0e4bgkl000113qcc0kgy38e https://status.qovery.com/incident/cm0e4bgkl000113qcc0kgy38e Managed Cluster deployment and update not available Type: Incident Duration: 5 hours and 32 minutes Affected Components: Infrastructure deployment May 23, 14:27:38 GMT+0 - Resolved - This incident has been resolved. May 23, 08:56:04 GMT+0 - Investigating - There is an issue with the deployment and update of the managed clusters We are currently investigating this incident. Type: Incident

Duration: 5 hours and 32 minutes

Affected Components:

May 23, 14:27:38 GMT+0
Resolved - This incident has been resolved..

May 23, 08:56:04 GMT+0
Investigating - There is an issue with the deployment and update of the managed clusters We are currently investigating this incident..

]]> Thu, 23 May 2024 08:56:04 +0000 https://status.qovery.com/incident/clwj0qao085803b6op1shu592f https://status.qovery.com/incident/clwj0qao085803b6op1shu592f Docker Builder Error Type: Incident Duration: 1 hour and 20 minutes Affected Components: Infrastructure deployment Mar 29, 20:20:06 GMT+0 - Resolved - This incident has been resolved. Mar 29, 19:30:28 GMT+0 - Monitoring - We provided a fix and we monitor that everything is fixed. Please retry your GitHub / GitLab / Bitbucket deployments. Mar 29, 19:03:20 GMT+0 - Identified - We are working on a fix for this incident. Impact: your GitHub / GitLab and Bitbucket applications might failed to be deployed with the error message "Cannot provision docker builder. Retrying..." - if it happens, wait a few minutes and then retry. Mar 29, 19:00:19 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 1 hour and 20 minutes

Affected Components:

Mar 29, 20:20:06 GMT+0
Resolved - This incident has been resolved..

Mar 29, 19:30:28 GMT+0
Monitoring - We provided a fix and we monitor that everything is fixed. Please retry your GitHub / GitLab / Bitbucket deployments..

Mar 29, 19:03:20 GMT+0
Identified - We are working on a fix for this incident. Impact: your GitHub / GitLab and Bitbucket applications might failed to be deployed with the error message "Cannot provision docker builder. Retrying..." - if it happens, wait a few minutes and then retry. .

Mar 29, 19:00:19 GMT+0
Investigating - We are currently investigating this incident..

]]> Fri, 29 Mar 2024 19:00:19 +0000 https://status.qovery.com/incident/clud13id4178805bcorermkgss3 https://status.qovery.com/incident/clud13id4178805bcorermkgss3 Kubernetes 1.28 upgrade for PRODUCTION clusters Type: Maintenance Duration: 2 days Affected Components: Infrastructure deployment, Environment deployment Mar 13, 08:00:00 GMT+0 - Completed - Maintenance has completed successfully Mar 11, 08:00:01 GMT+0 - Identified - Maintenance is now in progress Mar 11, 08:00:00 GMT+0 - Identified - As shared in [this post](https://discuss.qovery.com/t/important-kubernetes-upgrade-moving-to-1-27-1-28/2348), 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: Maintenance

Duration: 2 days

Affected Components: ,

Mar 13, 08:00:00 GMT+0
Completed - Maintenance has completed successfully.

Mar 11, 08:00:01 GMT+0
Identified - Maintenance is now in progress.

Mar 11, 08:00:00 GMT+0
Identified - As shared in [this post](https://discuss.qovery.com/t/important-kubernetes-upgrade-moving-to-1-27-1-28/2348), 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..

]]> Mon, 11 Mar 2024 08:00:00 +0000 https://status.qovery.com/maintenance/clsbynxco12109bnn6etsgq1gl https://status.qovery.com/maintenance/clsbynxco12109bnn6etsgq1gl Qovery maintenance Type: Maintenance Duration: 4 hours and 3 minutes Affected Components: Api, Infrastructure deployment, Environment deployment Mar 10, 18:02:56 GMT+0 - Completed - Maintenance has completed successfully. Mar 10, 14:00:01 GMT+0 - Identified - Maintenance is now in progress Mar 10, 14:00:00 GMT+0 - Identified - We are planning for scheduled maintenance during that time. Some services may be unresponsive for a few minutes during that time. So if you can't deploy/update/create/delete, please try again a few minutes later. There will be no impact on your infrastructure, services will continue to run as usual. Thanks for your understanding Type: Maintenance

Duration: 4 hours and 3 minutes

Affected Components: , ,

Mar 10, 18:02:56 GMT+0
Completed - Maintenance has completed successfully..

Mar 10, 14:00:01 GMT+0
Identified - Maintenance is now in progress.

Mar 10, 14:00:00 GMT+0
Identified - We are planning for scheduled maintenance during that time. Some services may be unresponsive for a few minutes during that time. So if you can't deploy/update/create/delete, please try again a few minutes later. There will be no impact on your infrastructure, services will continue to run as usual. Thanks for your understanding.

]]> Sun, 10 Mar 2024 14:00:00 +0000 https://status.qovery.com/maintenance/cltir7gz9268758b1n4vahd1yup https://status.qovery.com/maintenance/cltir7gz9268758b1n4vahd1yup Kubernetes 1.28 upgrade for NON-PRODUCTION clusters Type: Maintenance Duration: 2 days Affected Components: Environment deployment, Infrastructure deployment Feb 28, 08:00:00 GMT+0 - Completed - Maintenance has completed successfully Feb 26, 08:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 26, 08:00:00 GMT+0 - Identified - As shared in [this post](https://discuss.qovery.com/t/important-kubernetes-upgrade-moving-to-1-27-1-28/2348), 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 Type: Maintenance

Duration: 2 days

Affected Components: ,

Feb 28, 08:00:00 GMT+0
Completed - Maintenance has completed successfully.

Feb 26, 08:00:01 GMT+0
Identified - Maintenance is now in progress.

Feb 26, 08:00:00 GMT+0
Identified - As shared in [this post](https://discuss.qovery.com/t/important-kubernetes-upgrade-moving-to-1-27-1-28/2348), 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.

]]> Mon, 26 Feb 2024 08:00:00 +0000 https://status.qovery.com/maintenance/clsbym2q47723bnn6gwzgkcr1 https://status.qovery.com/maintenance/clsbym2q47723bnn6gwzgkcr1 Kubernetes 1.27 upgrade for PRODUCTION clusters Type: Maintenance Duration: 2 days Affected Components: Environment deployment, Infrastructure deployment Feb 28, 08:00:00 GMT+0 - Completed - Maintenance has completed successfully Feb 26, 08:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 26, 08:00:00 GMT+0 - Identified - As shared in [this ](https://discuss.qovery.com/t/important-kubernetes-upgrade-moving-to-1-27-1-28/2348)[post](https://discuss.qovery.com/t/important-kubernetes-upgrade-moving-to-1-27-1-28/2348), 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: Maintenance

Duration: 2 days

Affected Components: ,

Feb 28, 08:00:00 GMT+0
Completed - Maintenance has completed successfully.

Feb 26, 08:00:01 GMT+0
Identified - Maintenance is now in progress.

Feb 26, 08:00:00 GMT+0
Identified - As shared in [this ](https://discuss.qovery.com/t/important-kubernetes-upgrade-moving-to-1-27-1-28/2348)[post](https://discuss.qovery.com/t/important-kubernetes-upgrade-moving-to-1-27-1-28/2348), 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..

]]> Mon, 26 Feb 2024 08:00:00 +0000 https://status.qovery.com/maintenance/clsbxt5fr22430c4oouyomgr1u https://status.qovery.com/maintenance/clsbxt5fr22430c4oouyomgr1u Kubernetes 1.27 upgrade for NON-PRODUCTION clusters Type: Maintenance Duration: 2 days Affected Components: Environment deployment, Infrastructure deployment Feb 14, 08:00:00 GMT+0 - Completed - Maintenance has completed successfully Feb 12, 08:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 12, 08:00:00 GMT+0 - Identified - As shared in [this post](https://discuss.qovery.com/t/important-kubernetes-upgrade-moving-to-1-27-1-28/2348), 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 Type: Maintenance

Duration: 2 days

Affected Components: ,

Feb 14, 08:00:00 GMT+0
Completed - Maintenance has completed successfully.

Feb 12, 08:00:01 GMT+0
Identified - Maintenance is now in progress.

Feb 12, 08:00:00 GMT+0
Identified - As shared in [this post](https://discuss.qovery.com/t/important-kubernetes-upgrade-moving-to-1-27-1-28/2348), 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.

]]> Mon, 12 Feb 2024 08:00:00 +0000 https://status.qovery.com/maintenance/clsbxk5f89337cboodk1vde0z https://status.qovery.com/maintenance/clsbxk5f89337cboodk1vde0z GCP - Cannot deploy applications / containers to GCP clusters Type: Incident Duration: 1 day, 5 hours and 31 minutes Affected Components: Third Party: Google Cloud Platform → Google Cloud DNS, Third Party: Google Cloud Platform → Google Compute Engine, Third Party: Google Cloud Platform → Google Cloud Networking, Third Party: Google Cloud Platform → Google Cloud Storage, Third Party: Google Cloud Platform → Google Kubernetes Engine, Third Party: Google Cloud Platform → Identity & Access Management, Environment deployment Jan 26, 11:31:58 GMT+0 - Resolved - This incident has been resolved. Jan 25, 06:01:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Type: Incident

Duration: 1 day, 5 hours and 31 minutes

Affected Components: , , , , , ,

Jan 26, 11:31:58 GMT+0
Resolved - This incident has been resolved..

Jan 25, 06:01:00 GMT+0
Identified - We are continuing to work on a fix for this incident..

]]> Thu, 25 Jan 2024 06:01:00 +0000 https://status.qovery.com/incident/clrtd7ldo5797bincfv8vtuum https://status.qovery.com/incident/clrtd7ldo5797bincfv8vtuum Qovery console maintenance Type: Maintenance Duration: 19 minutes Affected Components: Console Jan 10, 13:19:01 GMT+0 - Completed - Maintenance has completed successfully. Jan 10, 13:00:01 GMT+0 - Identified - Maintenance is now in progress Jan 10, 13:00:00 GMT+0 - Identified - Qovery console will be under maintenance at 2PM CET time. The console will be randomly available in the hour. This maintenance is made to strongly enhance Qovery console reliability and speed up assets loading. Type: Maintenance

Duration: 19 minutes

Affected Components:

Jan 10, 13:19:01 GMT+0
Completed - Maintenance has completed successfully..

Jan 10, 13:00:01 GMT+0
Identified - Maintenance is now in progress.

Jan 10, 13:00:00 GMT+0
Identified - Qovery console will be under maintenance at 2PM CET time. The console will be randomly available in the hour. This maintenance is made to strongly enhance Qovery console reliability and speed up assets loading..

]]> Wed, 10 Jan 2024 13:00:00 +0000 https://status.qovery.com/maintenance/clr4sk2q647810b4o8te2izzeu https://status.qovery.com/maintenance/clr4sk2q647810b4o8te2izzeu Invitation emails not sent Type: Incident Duration: 7 days, 18 hours and 44 minutes Affected Components: Emails Nov 11, 10:43:24 GMT+0 - Resolved - This incident has been resolved. Nov 8, 11:35:15 GMT+0 - Identified - We will change our email service provider in the coming days to fix this incident. At the moment, please use the workaround below. Nov 6, 17:08:07 GMT+0 - Identified - **Our Email provider is still investigating.** We are continuing to work on a fix for this incident. Please keep using our workaround (cf last incident messages) Nov 4, 15:56:56 GMT+0 - Identified - Our Email provider is investigating. We are continuing to work on a fix for this incident. Please keep using our workaround (cf last incident messages) Nov 3, 23:34:29 GMT+0 - Identified - We identified that the issue is coming from our Email Provider. We are continuing to work on a fix for this incident. Please keep applying the workaround below at the moment. Nov 3, 15:59:14 GMT+0 - Investigating - We are currently investigating this incident. In the meantime, please copy and share manually the invitation link with your user. ![iamge](https://i.ibb.co/ZdWMnkY/Clean-Shot-2023-11-03-at-4-57-07.png) Type: Incident

Duration: 7 days, 18 hours and 44 minutes

Affected Components:

Nov 11, 10:43:24 GMT+0
Resolved - This incident has been resolved..

Nov 8, 11:35:15 GMT+0
Identified - We will change our email service provider in the coming days to fix this incident. At the moment, please use the workaround below. .

Nov 6, 17:08:07 GMT+0
Identified - **Our Email provider is still investigating.** We are continuing to work on a fix for this incident. Please keep using our workaround (cf last incident messages).

Nov 4, 15:56:56 GMT+0
Identified - Our Email provider is investigating. We are continuing to work on a fix for this incident. Please keep using our workaround (cf last incident messages).

Nov 3, 23:34:29 GMT+0
Identified - We identified that the issue is coming from our Email Provider. We are continuing to work on a fix for this incident. Please keep applying the workaround below at the moment. .

Nov 3, 15:59:14 GMT+0
Investigating - We are currently investigating this incident. In the meantime, please copy and share manually the invitation link with your user. ![iamge](https://i.ibb.co/ZdWMnkY/Clean-Shot-2023-11-03-at-4-57-07.png).

]]> Fri, 3 Nov 2023 15:59:14 +0000 https://status.qovery.com/incident/cloiswffl13804b8o4fj4tz5gx https://status.qovery.com/incident/cloiswffl13804b8o4fj4tz5gx Kubernetes 1.26 upgrade for PRODUCTION clusters Type: Maintenance Duration: 7 hours and 33 minutes Affected Components: Environment deployment, Infrastructure deployment Jul 24, 15:32:53 GMT+0 - Completed - Maintenance has completed successfully. Jul 24, 08:40:07 GMT+0 - Identified - Maintenance is now in progress. Jul 24, 08:00:00 GMT+0 - Identified - As shared in [this post](https://discuss.qovery.com/t/important-kubernetes-upgrade-moving-to-1-24-1-25-1-26/1916), 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: Maintenance

Duration: 7 hours and 33 minutes

Affected Components: ,

Jul 24, 15:32:53 GMT+0
Completed - Maintenance has completed successfully..

Jul 24, 08:40:07 GMT+0
Identified - Maintenance is now in progress..

Jul 24, 08:00:00 GMT+0
Identified - As shared in [this post](https://discuss.qovery.com/t/important-kubernetes-upgrade-moving-to-1-24-1-25-1-26/1916), 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. .

]]> Mon, 24 Jul 2023 08:00:00 +0000 https://status.qovery.com/maintenance/cliiyhewn999940apn82c7c4z68 https://status.qovery.com/maintenance/cliiyhewn999940apn82c7c4z68 Kubernetes 1.26 upgrade for NON-PRODUCTION clusters Type: Maintenance Duration: 22 hours and 59 minutes Affected Components: Environment deployment, Infrastructure deployment Jul 18, 06:59:19 GMT+0 - Completed - All non-production cluster have successfully been migrated to 1.26! Jul 17, 08:51:22 GMT+0 - Identified - Maintenance is now in progress. Jul 17, 08:00:00 GMT+0 - Identified - As shared in [this post](https://discuss.qovery.com/t/important-kubernetes-upgrade-moving-to-1-24-1-25-1-26/1916), 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 Type: Maintenance

Duration: 22 hours and 59 minutes

Affected Components: ,

Jul 18, 06:59:19 GMT+0
Completed - All non-production cluster have successfully been migrated to 1.26!.

Jul 17, 08:51:22 GMT+0
Identified - Maintenance is now in progress..

Jul 17, 08:00:00 GMT+0
Identified - As shared in [this post](https://discuss.qovery.com/t/important-kubernetes-upgrade-moving-to-1-24-1-25-1-26/1916), 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.

]]> Mon, 17 Jul 2023 08:00:00 +0000 https://status.qovery.com/maintenance/cliiyf100994542awn8k0eoo3mu https://status.qovery.com/maintenance/cliiyf100994542awn8k0eoo3mu Kubernetes 1.25 upgrade for PRODUCTION clusters Type: Maintenance Affected Components: Environment deployment, Infrastructure deployment Jul 10, 08:37:57 GMT+0 - Identified - Maintenance is now in progress. Jul 10, 08:34:09 GMT+0 - Completed - As shared in [this post](https://discuss.qovery.com/t/important-kubernetes-upgrade-moving-to-1-24-1-25-1-26/1916), 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: Maintenance

Affected Components: ,

Jul 10, 08:37:57 GMT+0
Identified - Maintenance is now in progress..

Jul 10, 08:34:09 GMT+0
Completed - As shared in [this post](https://discuss.qovery.com/t/important-kubernetes-upgrade-moving-to-1-24-1-25-1-26/1916), 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. .

]]> Mon, 10 Jul 2023 08:34:09 +0000 https://status.qovery.com/maintenance/cljwly4l2387844b3ohozcmfbvy https://status.qovery.com/maintenance/cljwly4l2387844b3ohozcmfbvy Qovery internal services outage Type: Incident Duration: 1 hour and 34 minutes Affected Components: Environment deployment, Infrastructure deployment, Api, Console Jul 7, 10:53:34 GMT+0 - Resolved - This incident has been resolved. Jul 7, 09:19:23 GMT+0 - Resolved - We are facing a major internal services issue, we are investigating in with AWS support. Console, API and Terraform are not available for the time being, but your clusters and services are not impacted. Type: Incident

Duration: 1 hour and 34 minutes

Affected Components: , , ,

Jul 7, 10:53:34 GMT+0
Resolved - This incident has been resolved..

Jul 7, 09:19:23 GMT+0
Resolved - We are facing a major internal services issue, we are investigating in with AWS support. Console, API and Terraform are not available for the time being, but your clusters and services are not impacted. .

]]> Fri, 7 Jul 2023 09:19:23 +0000 https://status.qovery.com/incident/cljsd7u58404965zoaugvsy12s https://status.qovery.com/incident/cljsd7u58404965zoaugvsy12s Qovery maintenance Type: Maintenance Duration: 6 hours and 24 minutes Affected Components: Environment deployment, Infrastructure deployment, Api, Console Jul 7, 13:23:44 GMT+0 - Completed - Maintenance has completed successfully. Jul 7, 07:00:00 GMT+0 - Identified - We are planning for scheduled maintenance during that time. Some services may be unresponsive for a few minutes during that time. So if you can't deploy/update/create/delete, please try again a few minutes later. There will be no impact on your infrastructure, services will continue to run as usual. Thanks for your understanding Type: Maintenance

Duration: 6 hours and 24 minutes

Affected Components: , , ,

Jul 7, 13:23:44 GMT+0
Completed - Maintenance has completed successfully..

Jul 7, 07:00:00 GMT+0
Identified - We are planning for scheduled maintenance during that time. Some services may be unresponsive for a few minutes during that time. So if you can't deploy/update/create/delete, please try again a few minutes later. There will be no impact on your infrastructure, services will continue to run as usual. Thanks for your understanding.

]]> Fri, 7 Jul 2023 07:00:00 +0000 https://status.qovery.com/maintenance/cljs7jf4k716680b6ollij9h7i1 https://status.qovery.com/maintenance/cljs7jf4k716680b6ollij9h7i1 Stuck application deployments Type: Incident Duration: 5 days, 21 hours and 22 minutes Affected Components: Api, Infrastructure deployment, Environment deployment, Console Jul 3, 12:25:59 GMT+0 - Resolved - This incident has been resolved. Jun 28, 08:30:15 GMT+0 - Monitoring - Deployment has been unblocked, we keep investigating on the reason. Jun 27, 15:38:12 GMT+0 - Investigating - The root cause is not identified yet. We're resetting the wrong status to unlock stuck deployments and keep investigating the issue. Jun 27, 15:04:08 GMT+0 - Investigating - Hi, Several customers reported issues with the application's deployments. Deployments occurs but last success message is not received, so deployments look stuck. We are currently investigating this incident. Sorry for the inconvenience Type: Incident

Duration: 5 days, 21 hours and 22 minutes

Affected Components: , , ,

Jul 3, 12:25:59 GMT+0
Resolved - This incident has been resolved..

Jun 28, 08:30:15 GMT+0
Monitoring - Deployment has been unblocked, we keep investigating on the reason..

Jun 27, 15:38:12 GMT+0
Investigating - The root cause is not identified yet. We're resetting the wrong status to unlock stuck deployments and keep investigating the issue..

Jun 27, 15:04:08 GMT+0
Investigating - Hi, Several customers reported issues with the application's deployments. Deployments occurs but last success message is not received, so deployments look stuck. We are currently investigating this incident. Sorry for the inconvenience.

]]> Tue, 27 Jun 2023 15:04:08 +0000 https://status.qovery.com/incident/cljef4oio17869csodsgmy6v10 https://status.qovery.com/incident/cljef4oio17869csodsgmy6v10 Database operations (create / update / delete) are failing Type: Incident Duration: 1 hour and 9 minutes Affected Components: Environment deployment May 17, 14:08:53 GMT+0 - Resolved - This incident has been resolved. May 17, 12:59:25 GMT+0 - Identified - Database deployments (creation, update, or deletion) are failing. Issue has been identified, a fix is on its way. Type: Incident

Duration: 1 hour and 9 minutes

Affected Components:

May 17, 14:08:53 GMT+0
Resolved - This incident has been resolved..

May 17, 12:59:25 GMT+0
Identified - Database deployments (creation, update, or deletion) are failing. Issue has been identified, a fix is on its way..

]]> Wed, 17 May 2023 12:59:25 +0000 https://status.qovery.com/incident/clhrpmd871493713vn2sou27c56 https://status.qovery.com/incident/clhrpmd871493713vn2sou27c56 Production incident Type: Incident Duration: 1 hour and 37 minutes Affected Components: Api, Third Party: BitBucket -> Webhooks, Console, Third Party: Github → Issues, Third Party: Amazon Web Services (AWS) → AWS eks-us-west-2, Third Party: Amazon Web Services (AWS) → AWS eks-eu-west-3, Third Party: Amazon Web Services (AWS) → AWS eks-eu-west-2, Third Party: BitBucket → Authentication and user management, Third Party: BitBucket → API, Third Party: Github → API Requests, Third Party: BitBucket → Git via HTTPS, Third Party: Github → Pull Requests, Third Party: BitBucket → Git via SSH, Third Party: Amazon Web Services (AWS) → AWS eks-us-east-1, Third Party: GitLab → Git Operations, Third Party: GitLab → API, Third Party: Scaleway → Elements - Products → Container Registry, Third Party: Scaleway → Elements - Products → Block Storage, Third Party: Auth0 → Europe (PROD) → Auth0 Machine to Machine Authentication, Third Party: Scaleway → Elements - AZ → pl-waw-1, Third Party: Scaleway → Elements - AZ → nl-ams-2, Infrastructure deployment, Third Party: Scaleway → Elements - AZ → nl-ams-1, Third Party: Scaleway → Elements - AZ → fr-par-3, Third Party: Scaleway → Elements - Products → LBaaS, Third Party: Scaleway → Elements - AZ → fr-par-2, Third Party: Scaleway → Elements - AZ → fr-par-1, Third Party: Scaleway → Elements - Products → Object Storage, Third Party: Scaleway → Elements - Products → Kapsule, Third Party: Scaleway → Elements - Products → Elastic Metal, AWS, Third Party: Amazon Web Services (AWS) → AWS ec2-eu-west-2, Third Party: Amazon Web Services (AWS) → AWS eks-ca-central-1, Third Party: Amazon Web Services (AWS) → AWS eks-ap-south-1, Third Party: Amazon Web Services (AWS) → AWS ec2-af-south-1, Third Party: Amazon Web Services (AWS) → AWS ec2-ap-northeast-3, Third Party: Amazon Web Services (AWS) → AWS eks-ap-southeast-1, Third Party: Amazon Web Services (AWS) → AWS ec2-eu-west-1, Third Party: Amazon Web Services (AWS) → AWS ec2-ap-east-1, Third Party: Amazon Web Services (AWS) → AWS ec2-us-east-2, Third Party: Amazon Web Services (AWS) → AWS ec2-eu-north-1, Third Party: Amazon Web Services (AWS) → AWS eks-ap-northeast-1, Third Party: Amazon Web Services (AWS) → AWS eks-ap-northeast-2, Third Party: Amazon Web Services (AWS) → AWS eks-eu-west-1, Third Party: Amazon Web Services (AWS) → AWS ec2-us-west-2, Third Party: Amazon Web Services (AWS) → AWS ec2-eu-central-1, Third Party: Auth0 → Europe (PROD) → Auth0 User Authentication, Third Party: Auth0 → Europe (PROD) → Auth0 Multi-factor Authentication, Third Party: GitLab → SAML SSO - GitLab SaaS, Third Party: Amazon Web Services (AWS) → AWS ec2-ca-central-1, Third Party: Amazon Web Services (AWS) → AWS ec2-eu-south-1, Third Party: Amazon Web Services (AWS) → AWS ec2-eu-west-3, Third Party: Github -> Webhooks, Third Party: Github → Git Operations, Environment deployment, Third Party: Amazon Web Services (AWS) → AWS eks-ap-southeast-2, Third Party: Amazon Web Services (AWS) → AWS eks-us-east-2, Third Party: Let's Encrypt → acme-v02.api.letsencrypt.org, Third Party: Amazon Web Services (AWS) → AWS ec2-ap-northeast-1, Third Party: Amazon Web Services (AWS) → AWS ec2-ap-southeast-1, Third Party: Amazon Web Services (AWS) → AWS eks-eu-central-1, Third Party: Amazon Web Services (AWS) → AWS eks-eu-north-1, Third Party: Cloudflare → Cloudflare Sites and Services → Authoritative DNS, Third Party: Amazon Web Services (AWS) → AWS ec2-ap-northeast-2, Third Party: Amazon Web Services (AWS) → AWS ec2-us-east-1, Third Party: Amazon Web Services (AWS) → AWS ec2-ap-southeast-2, Scaleway Feb 24, 16:05:26 GMT+0 - Resolved - We just resolved the issue! Feb 24, 15:14:55 GMT+0 - Monitoring - We implemented a fix and currently monitoring the result. Feb 24, 14:38:43 GMT+0 - Identified - We are continuing to work on a fix for this incident. Feb 24, 14:36:03 GMT+0 - Resolved - We just resolved the issue! Feb 24, 14:27:58 GMT+0 - Identified - We are facing a production incent. Issue is identified and being working on. Type: Incident

Duration: 1 hour and 37 minutes

Affected Components: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Feb 24, 16:05:26 GMT+0
Resolved - We just resolved the issue!.

Feb 24, 15:14:55 GMT+0
Monitoring - We implemented a fix and currently monitoring the result..

Feb 24, 14:38:43 GMT+0
Identified - We are continuing to work on a fix for this incident..

Feb 24, 14:36:03 GMT+0
Resolved - We just resolved the issue!.

Feb 24, 14:27:58 GMT+0
Identified - We are facing a production incent. Issue is identified and being working on..

]]> Fri, 24 Feb 2023 14:27:58 +0000 https://status.qovery.com/incident/cleimodwa350169qxn4ggqdgfli https://status.qovery.com/incident/cleimodwa350169qxn4ggqdgfli Deployments might get stuck in deploying state Type: Incident Duration: 3 hours and 6 minutes Affected Components: Environment deployment Jan 24, 20:00:29 GMT+0 - Resolved - We just resolved the issue! Jan 24, 16:54:03 GMT+0 - Investigating - We are currently investigating this incident. Waiting for a fix to be released, we are regularly unblocking the stuck deployments by marking them as failed. Type: Incident

Duration: 3 hours and 6 minutes

Affected Components:

Jan 24, 20:00:29 GMT+0
Resolved - We just resolved the issue!.

Jan 24, 16:54:03 GMT+0
Investigating - We are currently investigating this incident. Waiting for a fix to be released, we are regularly unblocking the stuck deployments by marking them as failed..

]]> Tue, 24 Jan 2023 16:54:03 +0000 https://status.qovery.com/incident/cldah8u455194zsn605jm5l25 https://status.qovery.com/incident/cldah8u455194zsn605jm5l25