Health check too slow

Hi Paul,
I am curious why Health Check is so slow. It was running for 11 minutes (and did not finish yet!).
I am expecting that the check will run for 1-2 minutes maximum and report me a list of machines which did not respond withing 1-2 minutes

See attached images


To handle remote environments with constrained bandwidth we increases the open connection timeout, which also means it takes longer for the health check to fail. With our current communication stack we have to make a trade off, but with 2.0 we plan to allow a few more controls around this so the health check should return much faster.


are you kidding about constrained bandwidth? =) It’s 21st century and almost everyone has 10+ MBit/sec connection. Do you expect someone to use Octopus with “Edge” or “Dial-up”? =))