Yep, you can configure the number of failed requests to make it unhealthy, and number of successful ones to mark it healthy, also the timeout, and the polling t

Yep, you can configure the number of failed requests to make it unhealthy, and number of successful ones to mark it healthy, also the timeout, and the polling time (e.g. every 30 seconds). But as others also pointed out, you can still get some "captured" servers until the LB realizes the machine is not super fast but simply superbad. Also your health check URL might return 200 and the rest of your app 404 / 500, which makes me think Perhaps the LB should be aware that if it gets back way more 404 and 500 than average for known URLs, then this should be considered as a bad server... I assume advanced LBs support that?