Qovery - Qovery Console and API maintenance – Maintenance details
Experiencing minor outage
Qovery Console and API maintenance
Completed
Scheduled for March 31, 2022 at 3:00 PM – 4:07 PM
Affects
Qovery
Under maintenance from 3:00 PM to 4:07 PM
Console
Under maintenance from 3:00 PM to 4:07 PM
Api
Under maintenance from 3:00 PM to 4:07 PM
Environment deployment
Under maintenance from 3:00 PM to 4:07 PM
Infrastructure deployment
Under maintenance from 3:00 PM to 4:07 PM
Updates
Completed
March 31, 2022 at 4:07 PM
Completed
March 31, 2022 at 4:07 PM
Maintenance has completed successfully.
In progress
March 31, 2022 at 3:04 PM
In progress
March 31, 2022 at 3:04 PM
Maintenance is now in progress.
Planned
March 31, 2022 at 3:00 PM
Planned
March 31, 2022 at 3:00 PM
Hi,
We wanted to inform you that a maintenance operation will be done on our platforms the 31/03/2021 at 3 pm UTC. The operation will last for a maximum of 2 hours and will cause a downtime of our console (console.qovery.com) and our API (api.qovery.com)
During this downtime period:
The infrastructures and services you have deployed on your cloud provider thanks to Qovery will continue to run during the whole operation. This maintenance operation will be completely transparent for your infrastructures and services since it impacts only our internal systems.
You will not be able to access the Qovery console or interact with the Qovery API (via the Git provider webhook calls, CLI, Github actions, terraform provider etc..)
An email will be sent before and after the maintenance operation to keep you updated with the status.
Tips to limit the downtime impact:
You won't be able to deploy your applications with Qovery during this downtime period, carefully plan your releases before this maintenance operation.
If your auto-deploy option is activated on Qovery side and you have merged new code during the downtime, don't forget to launch a manual deployment to align the environment with the latest code.
If in your CI/CD you have any script interacting with the Qovery API (Github actions, terraform, custom scripts, etc..), ensure that they won't block your pipeline during the downtime.
Feel free to contact us if you have any questions.