this is the replay from hosting company
======
The current implementation is a multi-pod/multi-server deployment which is different from a single server delpoyment as it tests every 10 seconds if the application code is up and running and healthy.
This health check is performed by testing one endpoint if it returns a sucess status code “200 OK”
The health check tests the path /wp-login.php if it responds correctly to determine if service is healthy or it should replace it with a new service to ensure service is always up and running.
The Plugins you are installing do change this path dynamically so health checks always assume service is not healthy and gives a wrong code and tries to initiate new ones constantly.
Most of similar plugins to provide a static path for login or a token to be used a an endpoint such as login?123456 for example which we can use to recnofigure the health check once the plugin is active to ensure health checks do not get false responses.
Please consult with your plugin provider if a similar setup or endpoint exists so we can take that into consideration.
========
