» Published on
The incident is over.
» UpdatedAll databases restarted on the impacted node. We are running our post-incident checks.
All databases are up and running. Please reach the support if this is not the case for your database.
» UpdatedWe are restarting the databases instances on the impacted node.
» UpdatedDocker restarted on the impacted node, our internal tools are now restarting.
» UpdatedThe restart of Docker on the impacted node is taking a bit more time than usual. The operation is still ongoing.
» UpdatedAn unplanned maintenance is needed on one of the nodes hosting databases. This maintenance requires a restart of Docker on this node. This operation takes a few minutes.
Databases using Business plans will automatically failover. The automatic failover procedure may induce a short unavailability (a few seconds).
Databases using Starter and Sandbox plans hosted on it will automatically be restarted after the successful restart of the node.
» Updated