Qovery - Notice history

All systems operational

100.0% uptime

Console - Operational

100.0% uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Api - Operational

100.0% uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Environment deployment - Operational

100.0% uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Infrastructure deployment - Operational

100.0% uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Emails - Operational

100.0% uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Customer infratructure - Operational

100.0% uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Terraform provider - Operational

100.0% uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025
100.0% uptime

Third Party: Scaleway → Elements - Products → Elastic Metal - Degraded performance

Third Party: Scaleway → Elements - Products → Kapsule - Operational

Third Party: Scaleway → Elements - Products → LBaaS - Operational

Third Party: Scaleway → Elements - Products → Object Storage - Operational

Third Party: Scaleway → Elements - Products → Container Registry - Operational

Third Party: Scaleway → Elements - Products → Block Storage - Operational

Third Party: Scaleway → Elements - AZ → fr-par-1 - Operational

Third Party: Scaleway → Elements - AZ → fr-par-2 - Operational

Third Party: Scaleway → Elements - AZ → fr-par-3 - Operational

Third Party: Scaleway → Elements - AZ → nl-ams-1 - Operational

Third Party: Scaleway → Elements - AZ → nl-ams-2 - Operational

Third Party: Scaleway → Elements - AZ → pl-waw-1 - Operational

Notice history

View current status

Apr 2025

APR14
Qovery maintenance
CompletedMaintenance3 hours 35 minutes
  • CompletedApril 14, 2025 at 11:35 AMUTC

    maintenance completed!

  • UpdateApril 14, 2025 at 9:00 AMUTC

    We are planning for a scheduled maintenance during that time.
    https://discuss.qovery.com/t/important-qovery-maintenance-03-17-2024-from-9am-to-11am-paris-time/6818

  • PlannedApril 14, 2025 at 8:00 AMUTC

    Maintenance rescheduled to the 04/14/2025

  • In progressApril 14, 2025 at 7:58 AMUTC

    Maintenance has started. You might experience some failure while connecting to our console, using our CLI/Terraform provider or connecting to our API. Some deployment requests might not be triggered

    We will write an update here when the upgrade is completed

Application Auto-deploy not working on GitHub
Resolved1 hour 37 minutes
  • ResolvedUTC

    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.

  • IdentifiedUTC

    The issue is present only on GitHub and it is due to a recent change in the payload sent by Github https://github.blog/changelog/

    We are working on a fix

  • InvestigatingUTC

    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

Mar 2025

MAR10
Kubernetes upgrade 1.31 - PRODUCTION clusters
CompletedMaintenance24 hours 38 minutes
  • CompletedMarch 11, 2025 at 8:39 AMUTC

    The cluster upgrade has been completed the 10/03!

  • In progressMarch 10, 2025 at 8:01 AMUTC
    Maintenance is now in progress
  • PlannedMarch 10, 2025 at 8:01 AMUTC

    As shared in this post, 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 have yet a precise time when we will trigger the update, we will keep you informed as soon as we have more visibility

environment/services displayed as "stopped" + SSH/port-forward not working
ResolvedDegraded performance57 minutes
  • ResolvedUTC

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

  • MonitoringUTC

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

  • IdentifiedUTC

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

  • InvestigatingUTC

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

MAR3
Kubernetes upgrade 1.31 - NON-PRODUCTION clusters
CompletedMaintenance48 hours 20 minutes
  • CompletedMarch 05, 2025 at 8:20 AMUTC
    Maintenance has completed successfully.
  • In progressMarch 03, 2025 at 8:00 AMUTC
    Maintenance is now in progress
  • PlannedMarch 03, 2025 at 8:00 AMUTC

    As shared in this post, 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 have yet a precise time when we will trigger the update, we will keep you informed as soon as we have more visibility

Feb 2025

No notices reported this month

Previous

Feb 2025 to Apr 2025

Next