Is Qovery down?

Last checked 4m ago
Current status
Qovery is up

No incidents right now.

Official status page: https://status.qovery.com · Polled every 5 minutes · 80 components tracked

Qovery is operational right now. Last checked 4m ago; the most recent incident resolved 8d ago.

Real-time Qovery status, recent outages, and incident history — pulled directly from Qovery's official status page at https://status.qovery.com every 5 minutes. Pingoru tracks 80 Qovery services and has captured 15 incidents in the last 90 days (99.83% uptime). Get email, Slack, Discord, or webhook alerts the moment Qovery reports a new incident — free for 5 monitors, no credit card.

Users who monitor Qovery also follow these Development services: Bitbucket OpenAI Datadog US1 Sentry NPM Travis CI Postman Pusher Pendo SonarCloud View all 6,000+ providers
Qovery uptime 99.83% uptime · past 90 days
Mon Wed Fri
AprMayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 14h 46m
    Started Jul 20, 2026, 05:00 PM UTC · Resolved Jul 21, 2026, 07:46 AM UTC
    Environment deploymentInfrastructure deployment
    Timeline · 3 updates
    • 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.

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

    • resolved · Jul 21, 2026, 07:46 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved
    Started Jul 20, 2026, 05:00 PM UTC · Resolved Jul 20, 2026, 05:00 PM UTC
    Timeline · 1 update
    • resolved · Jul 20, 2026, 05:00 PM UTC

      Type: Incident Duration: 14 hours and 46 minutes Affected Components: Environment deployment, Infrastructure deployment Jul 21, 07:46:27 GMT+0 - Resolved - This incident has been resolved. Jul 21, 10:18:51 GMT+0 - Postmortem - Jul 20, 17:00:22 GMT+0 - Investigating - All deployment jobs are currently stuck in the queue. We’re continuing to work on a fix for this incident. Jul 20, 18:33:21 GMT+0 - Monitoring - We’ve identified the issue. Everything is running smoothly now, and we’ll continue monitoring the situation. You can restart your stuck deployments.

    Latest: Type: Incident Duration: 14 hours and 46 minutes Affected Components: Environment deployment, Infrastructure deployment Jul 21, 07:46:27 GMT+0 - Resolved - This incident has been r…

  3. Resolved
    Started Jun 15, 2026, 07:00 AM UTC · Resolved Jun 15, 2026, 07:00 AM UTC
    Timeline · 1 update
    • 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

    Latest: 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/change…

  4. Resolved
    Started Jun 02, 2026, 03:00 PM UTC · Resolved Jun 02, 2026, 03:00 PM UTC
    Timeline · 1 update
    • 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.

    Latest: 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+…

  5. Resolved 4h
    Started Jun 02, 2026, 03:00 PM UTC · Resolved Jun 02, 2026, 07:00 PM UTC
    Terraform provider
    Timeline · 2 updates
    • 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.

    • resolved · Jun 02, 2026, 08:44 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full Qovery outage history

5 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Qovery outage history →

Or sign up free to get alerts when Qovery breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 10 incidents View full outage history →