Sweet, morning block! Good job BTCWoman.
Here are my stats for the hell of it, from Montreal Canada:
...
Thought id share my ping results as well. Just for reference.. i live 50 miles N/E from st louis about as centrally located in North america as one can get. I set a high packet amount just to test.. MTU is 1500 i usually ping test with just under the threshold.. You'd be surprised at how a server can easily handle 64 bytes but when you max out mtu it can really add to ping times.. i tried with both 64 and 1464 and didnt see any difference in response time.
C:\Users\d57he_000>ping -t -l 1464 de.kano.is
Pinging de.kano.is [139.162.143.142] with 1464 bytes of data
Reply from 139.162.143.142: bytes=1464 time=123ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=119ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=119ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=122ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=119ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=121ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=122ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=124ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=118ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=119ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=118ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=121ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=122ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=120ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=121ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=121ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=121ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=122ms TTL=50
Ping statistics for 139.162.143.142:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 118ms, Maximum = 124ms, Average = 120ms
Control-C
^C
C:\Users\d57he_000>ping -t -l 1464 sg.kano.is
Pinging sg.kano.is [139.162.5.112] with 1464 bytes of data:
Reply from 139.162.5.112: bytes=1464 time=245ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=242ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=244ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=242ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=247ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=246ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=242ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=242ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=241ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=247ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=240ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=244ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=249ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=245ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=250ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=246ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=266ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=288ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=291ms TTL=47
Ping statistics for 139.162.5.112:
Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 240ms, Maximum = 291ms, Average = 250ms
Control-C
^C
C:\Users\d57he_000>ping -t -l 1464 kano.is
Pinging kano.is [104.194.28.196] with 1464 bytes of data:
Reply from 104.194.28.196: bytes=1464 time=56ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=56ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=63ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=56ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=56ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=62ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=58ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=58ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=57ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=55ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=61ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=54ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=56ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=57ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=56ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=53ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=75ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=59ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=55ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=59ms TTL=49
Ping statistics for 104.194.28.196:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 75ms, Average = 58ms
Control-C
^C
C:\Users\d57he_000>
Best regards
d57heinz