Qovery - Notice history

All systems operational

100% - uptime

Console - Operational

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

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Api - Operational

100% - 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% - 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% - uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Emails - Operational

100% - 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% - uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Notice history

Apr 2025

Qovery maintenance
  • Completed
    April 14, 2025 at 11:35 AM
    Completed
    April 14, 2025 at 11:35 AM

    maintenance completed!

  • Update
    April 14, 2025 at 9:00 AM
    Planned
    April 14, 2025 at 9:00 AM

    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

  • Planned
    April 14, 2025 at 8:00 AM
    Planned
    April 14, 2025 at 8:00 AM

    Maintenance rescheduled to the 04/14/2025

  • In progress
    April 14, 2025 at 7:58 AM
    In progress
    April 14, 2025 at 7:58 AM

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

    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.

  • Identified
    Identified

    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

  • Investigating
    Investigating

    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

Kubernetes upgrade 1.31 - PRODUCTION clusters
  • Completed
    March 11, 2025 at 8:39 AM
    Completed
    March 11, 2025 at 8:39 AM

    The cluster upgrade has been completed the 10/03!

  • In progress
    March 10, 2025 at 8:01 AM
    In progress
    March 10, 2025 at 8:01 AM
    Maintenance is now in progress
  • Planned
    March 10, 2025 at 8:01 AM
    Planned
    March 10, 2025 at 8:01 AM

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

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

  • Monitoring
    Monitoring

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

  • Identified
    Identified

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

  • Investigating
    Investigating

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

Kubernetes upgrade 1.31 - NON-PRODUCTION clusters
  • Completed
    March 05, 2025 at 8:20 AM
    Completed
    March 05, 2025 at 8:20 AM
    Maintenance has completed successfully.
  • In progress
    March 03, 2025 at 8:00 AM
    In progress
    March 03, 2025 at 8:00 AM
    Maintenance is now in progress
  • Planned
    March 03, 2025 at 8:00 AM
    Planned
    March 03, 2025 at 8:00 AM

    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

Feb 2025 to Apr 2025

Next