Qovery incident

Kubernetes upgrade 1.35 - NON-PRODUCTION clusters

Minor Resolved View vendor source →

Qovery experienced a minor incident on June 1, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jun 01, 2026, 07:00 AM UTC
Resolved
Jun 01, 2026, 07:00 AM UTC
Duration
—
Detected by Pingoru
Jun 01, 2026, 07:00 AM UTC

Update timeline

  1. resolved Jun 01, 2026, 07:00 AM UTC

    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