Qovery incident

Kubernetes upgrade 1.33 - NON-PRODUCTION clusters

Minor Resolved View vendor source →

Qovery experienced a minor incident on September 22, 2025, lasting —. The incident has been resolved; the full update timeline is below.

Started
Sep 22, 2025, 07:00 AM UTC
Resolved
Sep 22, 2025, 07:00 AM UTC
Duration
—
Detected by Pingoru
Sep 22, 2025, 07:00 AM UTC

Update timeline

  1. resolved Sep 22, 2025, 07:00 AM UTC

    Type: Maintenance Duration: 6 hours and 10 minutes Affected Components: Customer infratructure Sep 22, 07:00:00 GMT+0 - Identified - As shared in [this post](https://discuss.qovery.com/t/important-qovery-managed-kubernetes-cluster-upgrade-moving-to-1-32-1-33/6822), we will start upgrading some of your Kubernetes clusters to the new version. This week, we will start by upgrading all your **NON-PRODUCTION** clusters. We do not yet have a precise time when we will trigger the update, but we will keep you informed as soon as we have more visibility Sep 22, 13:09:31 GMT+0 - Completed - All non-production clusters have been updated to Kubernetes 1.33 Sep 22, 07:00:01 GMT+0 - Identified - Maintenance is now in progress