EDIT: So i just went around testing pools. And deepbit has the best latency for me, That alone is reason enough for me to stay.
I call double bullshit on this. Deepbit servers are going over a transatlantic link for you, there is absolutely no way you get better latency to Deepbit than some other servers. Or did you mean you only tested ones that go over transoceanic links?
I shall start pinging again and post results, Because i have clearly made people mad...
Pinging deepbit.net [46.4.121.118] with 32 bytes of data:
Reply from 46.4.121.118: bytes=32 time=172ms TTL=53
Reply from 46.4.121.118: bytes=32 time=172ms TTL=53
Reply from 46.4.121.118: bytes=32 time=187ms TTL=53
Reply from 46.4.121.118: bytes=32 time=173ms TTL=53
Ping statistics for 46.4.121.118:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 172ms, Maximum = 187ms, Average = 176ms
Pinging pool.bitclockers.com [204.45.253.21] with 32 bytes of data:
Reply from 204.45.253.21: bytes=32 time=38ms TTL=55
Reply from 204.45.253.21: bytes=32 time=41ms TTL=55
Reply from 204.45.253.21: bytes=32 time=38ms TTL=55
Reply from 204.45.253.21: bytes=32 time=39ms TTL=55
Ping statistics for 204.45.253.21:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 41ms, Average = 39ms
Pinging mining.bitcoin.cz [176.31.157.133] with 32 bytes of data:
Reply from 176.31.157.133: bytes=32 time=169ms TTL=50
Reply from 176.31.157.133: bytes=32 time=169ms TTL=50
Reply from 176.31.157.133: bytes=32 time=168ms TTL=50
Reply from 176.31.157.133: bytes=32 time=168ms TTL=50
Ping statistics for 176.31.157.133:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 168ms, Maximum = 169ms, Average = 168ms
Pinging us.eclipsemc.com [208.110.68.114] with 32 bytes of data:
Reply from 208.110.68.114: bytes=32 time=86ms TTL=51
Reply from 208.110.68.114: bytes=32 time=88ms TTL=51
Reply from 208.110.68.114: bytes=32 time=86ms TTL=51
Reply from 208.110.68.114: bytes=32 time=74ms TTL=51
Ping statistics for 208.110.68.114:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 74ms, Maximum = 88ms, Average = 83ms
Pinging btcguild.com [108.60.208.157] with 32 bytes of data:
Reply from 108.60.208.157: bytes=32 time=125ms TTL=49
Reply from 108.60.208.157: bytes=32 time=128ms TTL=49
Reply from 108.60.208.157: bytes=32 time=126ms TTL=49
Reply from 108.60.208.157: bytes=32 time=131ms TTL=49
Ping statistics for 108.60.208.157:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 125ms, Maximum = 131ms, Average = 127ms
Pinging ra.mining.eligius.st [78.47.187.252] with 32 bytes of data:
Reply from 78.47.187.252: bytes=32 time=174ms TTL=53
Reply from 78.47.187.252: bytes=32 time=174ms TTL=53
Reply from 78.47.187.252: bytes=32 time=175ms TTL=53
Reply from 78.47.187.252: bytes=32 time=175ms TTL=53
Ping statistics for 78.47.187.252:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 174ms, Maximum = 175ms, Average = 174ms
hmmmmmmmmmm.... Clearly i am wrong.... I suppose i fucked up on my earlier testing? Somehow?
Edit: the dude below me stated where he was from, So i mayaswell do the same so that the two sets of pings can be compared.
From Canada!
Well... I would switch to BTCguild.. But they are Merged Mining,