Affected Components: Customer infratructure, Infrastructure deployment

Jun 15, 07:00:00 GMT+0
Identified - 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.

Affected Components: Customer infratructure, Infrastructure deployment

Jun 1, 07:00:00 GMT+0
Identified - 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.

Affected Components: Customer infratructure, Infrastructure deployment

May 11, 07:00:00 GMT+0
Identified - 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.

Affected Components: Customer infratructure, Infrastructure deployment

Apr 27, 07:00:00 GMT+0
Identified - 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.

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

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.

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

Duration: 52 minutes

Affected Components: Environment deployment, Api, Console, Infrastructure deployment

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

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

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

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.

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.

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

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

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

Duration: 3 hours and 38 minutes

Affected Components: Api, Emails, Console, Infrastructure deployment, Environment deployment, Customer infratructure

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, 11:35:59 GMT+0
Completed - maintenance completed!.

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.

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

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 <https://github.blog/changelog/> 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..

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.

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

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.

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.

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

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

Affected Components: Environment deployment

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

Duration: 4 hours

Affected Components: Infrastructure deployment, Environment deployment

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, 12:00:00 GMT+0
Completed - Maintenance has completed successfully.

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

Duration: 3 hours and 17 minutes

Affected Components: Customer infratructure

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.

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

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

Duration: 1 hour and 20 minutes

Affected Components: Infrastructure deployment

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

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

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

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

Duration: 4 hours and 3 minutes

Affected Components: Api, Infrastructure deployment, Environment deployment

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

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

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.

Duration: 2 days

Affected Components: Environment deployment, Infrastructure deployment

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

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

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.

Duration: 2 days

Affected Components: Environment deployment, Infrastructure deployment

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

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

Duration: 2 days

Affected Components: Environment deployment, Infrastructure deployment

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.

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

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

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 25, 06:01:00 GMT+0
Identified - We are continuing to work on a fix for this incident..

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

Duration: 19 minutes

Affected Components: Console

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

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.

Duration: 7 days, 18 hours and 44 minutes

Affected Components: Emails

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

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 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 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 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 11, 10:43:24 GMT+0
Resolved - This incident has been resolved..

Duration: 7 hours and 33 minutes

Affected Components: Environment deployment, Infrastructure deployment

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

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

Duration: 22 hours and 59 minutes

Affected Components: Environment deployment, Infrastructure deployment

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

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

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.

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

Duration: 1 hour and 34 minutes

Affected Components: Environment deployment, Infrastructure deployment, Api, Console

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

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

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.

Duration: 5 days, 21 hours and 22 minutes

Affected Components: Api, Infrastructure deployment, Environment deployment, Console

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.

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 28, 08:30:15 GMT+0
Monitoring - Deployment has been unblocked, we keep investigating on the reason..

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

Affected Components: Infrastructure deployment, Environment deployment

Jun 26, 08:00:00 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. .

Duration: 1 hour and 9 minutes

Affected Components: Environment deployment

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

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

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, 14:27:58 GMT+0
Identified - We are facing a production incent. Issue is identified and being working on..

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

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

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

Duration: 3 hours and 6 minutes

Affected Components: Environment deployment

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

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

Duration: 1 hour and 19 minutes

Affected Components: Environment deployment

Jan 24, 10:16:40 GMT+0
Resolved - The fix has been released! The incident is now closed.

Jan 24, 08:57:58 GMT+0
Identified - Following a change in how they store internally their images, we are not using anymore the caching mechanism that was avoiding re-building your code each time. This means that your code might be rebuilt even if no change was done to it, increasing the deployment time. We are currently working on a fix. .

Duration: 37 minutes

Affected Components: Infrastructure deployment, Environment deployment, Api, Console

Oct 21, 07:32:34 GMT+0
Identified - The problem has been identified and we are working on a solution. The Qovery API is currently not available and it impacts the console and any direct integration with it. .

Oct 21, 08:09:39 GMT+0
Resolved - We just resolved the issue!.

Affected Components: Environment deployment

Sep 28, 10:31:10 GMT+0
Resolved - We are currently investigating this incident. It’s related to heroku recent change, removing compatibility with 20 builder version: [Releases · heroku/procfile-cnb · GitHub ](https://github.com/heroku/procfile-cnb/releases) Forum thread https://discuss.qovery.com/t/cannot-deploy-issue-with-a-buildpack/1454/8 .

Duration: 34 minutes

Affected Components: Console

Aug 18, 08:00:00 GMT+0
Investigating - Hi, We're facing an issue with the console TLS. We're digging into it to fix it. Thanks.

Aug 18, 08:34:22 GMT+0
Resolved - We just resolved the issue! We're still investigating why it has failed..

Duration: 1 minute

Affected Components: Api, Console

Aug 10, 08:55:52 GMT+0
Resolved - We just resolved the issue!.

Aug 10, 08:54:30 GMT+0
Investigating - We are currently investigating this incident..