Qovery Outage History

Qovery degraded View live status →

Qovery had 9 outages in the last 2 years totaling 4h 31m of downtime — averaging 0.4 incidents per month.

There were 9 Qovery outages since July 22, 2025 totaling 4h 31m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.qovery.com

Major June 2, 2026

Terraform provider

Detected by Pingoru
Jun 02, 2026, 03:00 PM UTC
Resolved
Jun 02, 2026, 07:00 PM UTC
Duration
4h
Affected: Qovery (Terraform provider)
Timeline · 2 updates
  1. resolved Jun 02, 2026, 07: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.

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 →