Qovery - Notice history

All systems operational

100% - uptime

Console - Operational

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

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Api - Operational

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

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Environment deployment - Operational

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

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Infrastructure deployment - Operational

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

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Emails - Operational

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

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Customer infratructure - Operational

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

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Terraform provider - Operational

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

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Notice history

Mar 2025

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

    The cluster upgrade has been completed the 10/03!

  • In progress
    March 10, 2025 at 8:01 AMUTC
    In progress
    March 10, 2025 at 8:01 AMUTC
    Maintenance is now in progress
  • Planned
    March 10, 2025 at 8:01 AMUTC
    Planned
    March 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
  • Resolved
    UTC
    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
    UTC
    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
    UTC
    Identified

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

  • Investigating
    UTC
    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 AMUTC
    Completed
    March 05, 2025 at 8:20 AMUTC
    Maintenance has completed successfully.
  • In progress
    March 03, 2025 at 8:00 AMUTC
    In progress
    March 03, 2025 at 8:00 AMUTC
    Maintenance is now in progress
  • Planned
    March 03, 2025 at 8:00 AMUTC
    Planned
    March 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

Jan 2025

Container deployment experiencing issues during the Mirroring step
  • Resolved
    UTC
    Resolved

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

  • Monitoring
    UTC
    Monitoring

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

  • Investigating
    UTC
    Investigating

    Container deployment is experiencing issues during the Mirroring step (long mirroring potentially failing)

    We are investigating

Jan 2025 to Mar 2025

Next