Qovery Outage History

Qovery is up right now

Pingoru has recorded 39 incidents for Qovery: 12 in the last 12 months and 5 in the last 90 days.

Source: status.qovery.com

39incidents recorded
12last 12 months
5last 90 days
4 hourstypical duration
Incidents per month
036AprMayJunJulAugSepOct5
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking Qovery in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202630 of 744 (0%)
June 202626 of 720 (1%)
July 2026215 of 744 (2%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202653 of 523 (1%)

Incidents, newest first

Major October 8, 2026 Console unreachable and authentication issues through the CLI 1h 44m Qovery (Console), Qovery (Api), Qovery (Environment deployment), Qovery (Infrastructure deployment) and 3 more

Started Oct 08, 2026, 10:50 AM UTC· resolved Oct 08, 2026, 12:34 PM UTC

  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 →

Minor October 8, 2026 Console access and CLI authentication issues 32m

Started Oct 08, 2026, 09:10 AM UTC· resolved Oct 08, 2026, 09:42 AM UTC

  1. investigating Oct 08, 2026, 09:10 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 14h 46m Qovery (Environment deployment), Qovery (Infrastructure deployment)

Started Jul 20, 2026, 05:00 PM UTC· resolved Jul 21, 2026, 07:46 AM UTC

  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 2, 2026 Terraform provider 5h 44m

Started Jun 02, 2026, 03:00 PM UTC· resolved Jun 02, 2026, 08:44 PM UTC

  1. resolved Jun 02, 2026, 03:00 PM UTC

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

  2. resolved Jun 02, 2026, 08:44 PM UTC

    This incident has been resolved..

  3. monitoring Jun 03, 2026, 03:18 PM UTC

    .

Read the full incident report →

Major May 22, 2026 Console down 15m Qovery (Console)

Started May 22, 2026, 01:47 PM UTC· resolved May 22, 2026, 02:02 PM UTC

  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 16m Qovery (Console)

Started May 22, 2026, 01:45 PM UTC· resolved May 22, 2026, 02:01 PM UTC

  1. investigating May 22, 2026, 01:45 PM UTC

    We are currently investigating this incident.

Read the full incident report →

Minor October 6, 2025 Kubernetes upgrade 1.33 - PRODUCTION clusters –

Started Oct 06, 2025, 07:00 AM UTC· resolved Oct 06, 2025, 07:00 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor September 22, 2025 Kubernetes upgrade 1.33 - NON-PRODUCTION clusters –

Started Sep 22, 2025, 07:00 AM UTC· resolved Sep 22, 2025, 07:00 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor September 8, 2025 Kubernetes upgrade 1.32 - PRODUCTION clusters –

Started Sep 08, 2025, 07:00 AM UTC· resolved Sep 08, 2025, 07:00 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor September 1, 2025 [AWS ONLY] Deployments failing due to IAM trust policy change 4h

Started Sep 01, 2025, 02:56 PM UTC· resolved Sep 01, 2025, 06:56 PM UTC

  1. identified Sep 01, 2025, 02:56 PM UTC

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

  2. resolved Sep 01, 2025, 06:56 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor August 25, 2025 Kubernetes upgrade 1.32 - NON-PRODUCTION clusters –

Started Aug 25, 2025, 07:00 AM UTC· resolved Aug 25, 2025, 07:00 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor July 22, 2025 TLS Certificate creation/renewal impacted for your application - Ongoing issue with Let's encrypt 4h 6m

Started Jul 22, 2025, 08:59 AM UTC· resolved Jul 22, 2025, 01:05 PM UTC

  1. identified Jul 22, 2025, 08:59 AM UTC

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

  2. resolved Jul 22, 2025, 01:05 PM UTC

    The incident has been solved by let's encrypt. Certificate generation and renewal is back to normal.

Read the full incident report →

Minor June 6, 2025 API TLS issue 40m

Started Jun 06, 2025, 05:40 PM UTC· resolved Jun 06, 2025, 06:20 PM UTC

  1. investigating Jun 06, 2025, 05:40 PM UTC

    We are currently investigating this incident..

  2. resolved Jun 06, 2025, 06:20 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor June 5, 2025 TLS issue on Qovery API 40m

Started Jun 05, 2025, 05:40 PM UTC· resolved Jun 05, 2025, 06:20 PM UTC

  1. investigating Jun 05, 2025, 05:40 PM UTC

    We are currently investigating this incident..

  2. resolved Jun 05, 2025, 06:20 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor May 26, 2025 Scaleway non-production cluster deployment issue. 5h 14m

Started May 26, 2025, 01:11 PM UTC· resolved May 26, 2025, 06:25 PM UTC

  1. investigating May 26, 2025, 01:11 PM UTC

    We are currently investigating this incident..

  2. identified May 26, 2025, 01:28 PM UTC

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

  3. resolved May 26, 2025, 06:25 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor April 8, 2025 Application Auto-deploy not working on GitHub 1h 37m

Started Apr 08, 2025, 04:07 PM UTC· resolved Apr 08, 2025, 05:45 PM UTC

  1. investigating Apr 08, 2025, 04:07 PM UTC

    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.

  2. identified Apr 08, 2025, 04:33 PM UTC

    The issue is present only on GitHub and it is due to a recent change in the payload sent by Github We are working on a fix.

  3. resolved Apr 08, 2025, 05:45 PM UTC

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

Read the full incident report →

Minor March 10, 2025 Kubernetes upgrade 1.31 - PRODUCTION clusters –

Started Mar 10, 2025, 08:01 AM UTC· resolved Mar 10, 2025, 08:01 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor March 3, 2025 environment/services displayed as "stopped" + SSH/port-forward not working 57m

Started Mar 03, 2025, 02:14 PM UTC· resolved Mar 03, 2025, 03:12 PM UTC

  1. investigating Mar 03, 2025, 02:14 PM UTC

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

  2. identified Mar 03, 2025, 02:45 PM UTC

    We have found the fix and re-deploying all the clusters.

  3. monitoring Mar 03, 2025, 03:10 PM UTC

    A fix has been deployed. It is possible you have to clear the browser cache (Ctrl + Shift + R) to see the statuses again..

  4. resolved Mar 03, 2025, 03:12 PM UTC

    A fix has been deployed. It is possible you have to clear the browser cache (Ctrl + Shift + R) to see the statuses again..

Read the full incident report →

Minor March 3, 2025 Kubernetes upgrade 1.31 - NON-PRODUCTION clusters –

Started Mar 03, 2025, 08:00 AM UTC· resolved Mar 03, 2025, 08:00 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor January 28, 2025 Container deployment experiencing issues during the Mirroring step 2h 2m

Started Jan 28, 2025, 04:28 PM UTC· resolved Jan 28, 2025, 06:31 PM UTC

  1. investigating Jan 28, 2025, 04:28 PM UTC

    Container deployment is experiencing issues during the Mirroring step (long mirroring potentially failing) We are investigating.

  2. monitoring Jan 28, 2025, 05:16 PM UTC

    The issue seems to have disappeared, we are trying to understand why.

  3. resolved Jan 28, 2025, 06:31 PM UTC

    The issue is finally closed but the root cause has not been identified (probably external).

Read the full incident report →

Minor November 12, 2024 Problem with PostgreSQL ContainerDB. 2h 34m

Started Nov 12, 2024, 01:00 PM UTC· resolved Nov 12, 2024, 03:34 PM UTC

  1. identified Nov 12, 2024, 01:00 PM UTC

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

  2. resolved Nov 12, 2024, 03:34 PM UTC

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

Read the full incident report →