Qovery Outage History

Qovery degraded View live status →

Qovery had 10 outages in the last 2 years totaling 17h 44m of downtime — averaging 0.4 incidents per month.

There were 10 Qovery outages since April 27, 2026 totaling 17h 44m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.qovery.com

Major October 8, 2026

Console unreachable and authentication issues through the CLI

Detected by Pingoru
Oct 08, 2026, 10:50 AM UTC
Resolved
Oct 08, 2026, 12:34 PM UTC
Duration
1h 44m
Affected: Qovery (Console)Qovery (Api)Qovery (Environment deployment)Qovery (Infrastructure deployment)Qovery (Emails)Qovery (Customer infratructure)Qovery (Terraform provider)
Timeline · 3 updates
  1. investigating Oct 08, 2026, 10:50 AM UTC

    We are currently investigating this incident.

  2. monitoring Oct 08, 2026, 10:57 AM UTC

    The situation has been stabilized and the team is keeping an eye on it.

  3. resolved Oct 08, 2026, 12:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 8, 2026

Console access and CLI authentication issues

Detected by Pingoru
Oct 08, 2026, 09:00 AM UTC
Resolved
Oct 08, 2026, 09:42 AM UTC
Duration
42m
Affected: Qovery (Console)Qovery (Api)Qovery (Environment deployment)Qovery (Infrastructure deployment)Qovery (Emails)Qovery (Customer infratructure)Qovery (Terraform provider)
Timeline · 3 updates
  1. investigating Oct 08, 2026, 09:00 AM UTC

    We are currently investigating this incident.

  2. monitoring Oct 08, 2026, 09:36 AM UTC

    We've deployed a fix for this incident. The console and CLI are now available again. The still is still monitoring the situation.

  3. resolved Oct 08, 2026, 09:42 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 20, 2026

All deployment jobs are currently stuck in the queue

Detected by Pingoru
Jul 20, 2026, 05:00 PM UTC
Resolved
Jul 21, 2026, 07:46 AM UTC
Duration
14h 46m
Affected: Qovery (Environment deployment)Qovery (Infrastructure deployment)
Timeline · 3 updates
  1. investigating Jul 20, 2026, 05:00 PM UTC

    All deployment jobs are currently stuck in the queue. We’re continuing to work on a fix for this incident.

  2. monitoring Jul 20, 2026, 06:33 PM UTC

    We’ve identified the issue. Everything is running smoothly now, and we’ll continue monitoring the situation. You can restart your stuck deployments.

  3. resolved Jul 21, 2026, 07:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 15, 2026

Kubernetes upgrade 1.35 - PRODUCTION clusters

Detected by Pingoru
Jun 15, 2026, 07:00 AM UTC
Resolved
Jun 15, 2026, 07:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 15, 2026, 07:00 AM UTC

    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

Read the full incident report →

Minor June 2, 2026

Terraform provider

Detected by Pingoru
Jun 02, 2026, 03:00 PM UTC
Resolved
Jun 02, 2026, 03:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 02, 2026, 03:00 PM UTC

    Type: Incident Affected Components: Terraform provider Jun 3, 15:18:17 GMT+0 - Postmortem - Jun 2, 20:44:33 GMT+0 - Resolved - This incident has been resolved. Jun 2, 15:00:00 GMT+0 - Resolved - This incident has been resolved. Our terraform provider was returning `unexpected error: 415 Unsupported Media Type - Could not parse Content-Type.` due to an incompatibility change on our reverse-proxy with our go qovery client sdk. We have rollbacked our change on the reverse proxy while we fix the issue in the client sdk.

Read the full incident report →

Minor June 1, 2026

Kubernetes upgrade 1.35 - NON-PRODUCTION clusters

Detected by Pingoru
Jun 01, 2026, 07:00 AM UTC
Resolved
Jun 01, 2026, 07:00 AM UTC
Duration
—
Timeline · 1 update
  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

Read the full incident report →

Major May 22, 2026

Console down

Detected by Pingoru
May 22, 2026, 01:47 PM UTC
Resolved
May 22, 2026, 02:02 PM UTC
Duration
15m
Affected: Qovery (Console)
Timeline · 5 updates
  1. identified May 22, 2026, 01:47 PM UTC

    The console is currently reported as down. We found the issue and are rolling back the failed change now.

  2. resolved May 22, 2026, 01:53 PM UTC

    This incident has been resolved.

  3. identified May 22, 2026, 01:57 PM UTC

    We are continuing to work on a fix for this incident.

  4. monitoring May 22, 2026, 02:02 PM UTC

    We implemented a fix and are currently monitoring the result.

  5. resolved May 22, 2026, 02:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 22, 2026

Console unavailability

Detected by Pingoru
May 22, 2026, 01:45 PM UTC
Resolved
May 22, 2026, 02:01 PM UTC
Duration
16m
Affected: Qovery (Console)
Timeline · 1 update
  1. investigating May 22, 2026, 01:45 PM UTC

    We are currently investigating this incident.

Read the full incident report →

Minor May 11, 2026

Kubernetes upgrade 1.34 - PRODUCTION clusters

Detected by Pingoru
May 11, 2026, 07:00 AM UTC
Resolved
May 11, 2026, 07:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved May 11, 2026, 07:00 AM UTC

    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

Read the full incident report →

Minor April 27, 2026

Kubernetes upgrade 1.34 - NON-PRODUCTION clusters

Detected by Pingoru
Apr 27, 2026, 07:00 AM UTC
Resolved
Apr 27, 2026, 07:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 27, 2026, 07:00 AM UTC

    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

Read the full incident report →