can anyone beat 11ms ping time on speedtest.net

[Leyawiin]

Heh - old subdivision with copper wires (and I don't do Comcast). I'm about sixty miles from the nearest server.

http://www.speedtest.net/my-result/3480901020

 

[dave_the_nerd]

Man, over wifi, I can't even ping my own router reliably in <11ms.

 

[ultimatebob]

OK... where is that bastard who works at Apple and basically has his own OC-768 to use. HE always wins these speed tests.

 

[zanejohnson]

lol i might be forced to seriously stess my shit tonight because of this zombie thread i made years ago.

 

[Red Squirrel]

Not terrible for DSL.

Yeah that's pretty good.

I don't even get that at work, and the local loop does not even go outside! :awe:

Though I think it's because people leave file transfers and other stuff running.

 

[master_shake_]

best i could do

 

[DigDog]

i used to have 10ms from london to maidenhead with BE. i would terrorize whole lobbies in QuakeLive with my uber LG.

sadly, no more.

 

[Gillbot]

seems to match speedtest pretty well:

 

[TROLLERCAUST]

30/1 Mbps cable. Shitty upload is shitty but enough for my use.

 

[DownTheSky]

Crappy router getting in the way. I used to get 1-2 ms.

 

[MrSquished]

 

[Tweak155]

Best I could get just now was 14. Guess it hasn't changed much.

 

[ch33zw1z]

finally got a day off, and I'm bored. Here's a test from an old school laptop running wireless g and debian 7.4 lxde

 

[sourceninja]

This is short term, we are waiting to bring up the 1gbps link until the first of the month.

 

[JBT]

 

[ch33zw1z]

speedtest from my main rig.

 

[ghost recon88]

I was able to get 450 download last summer

 

[Thebobo]

EAT MY PING!

......or lack there of it.

/brag off.

 

[pete6032]

EAT MY PING!

......or lack there of it.

/brag off.

Dang. I was so excited to post mine and then I saw yours. This is from work.

 

[thecoolnessrune]

I too can do low pings on campus or at the DataCenter.

It's a load of crap Your ping to a datacenter less than 100 miles from your house is completely irrelevant.

Look how much higher ping goes just going to Atlanta:

University of Alaska?

Try crossing Continents..

Aside from diagnosing severe local internet issues, the value in a ping to your nearest Datacenter is kind of pointless

 

[Lean L]

I thought I could beat it but maybe not.


http@server ~ $ speedtest
Retrieving speedtest.net configuration...
Retrieving speedtest.net server list...
Testing from Comcast Cable (x.x.x.x)...
Selecting best server based on ping...
Hosted by Atlantic Metro (New York City, NY) [115.98 km]: 11.683 ms
Testing download speed........................................
Download: 117.19 Mbit/s
Testing upload speed..................................................
Upload: 11.28 Mbit/s

 

[ultimatebob]

I think that the 100 megabit Ethernet connection to my laptop is the bottleneck at this point. My side of the office hasn't been upgraded to Gigabit yet.

 

[Red Squirrel]

EAT MY PING!

......or lack there of it.

/brag off.

Are you hosting a speedtest server in your basement or something?

Only way I can get pings that low is locally. :awe:

root@falcon:~# ping borg.loc
PING borg.loc (10.1.1.10) 56(84) bytes of data.
64 bytes from borg.loc (10.1.1.10): icmp_seq=1 ttl=64 time=0.167 ms
64 bytes from borg.loc (10.1.1.10): icmp_seq=2 ttl=64 time=0.200 ms
64 bytes from borg.loc (10.1.1.10): icmp_seq=3 ttl=64 time=0.204 ms
64 bytes from borg.loc (10.1.1.10): icmp_seq=4 ttl=64 time=0.254 ms
64 bytes from borg.loc (10.1.1.10): icmp_seq=5 ttl=64 time=0.179 ms
64 bytes from borg.loc (10.1.1.10): icmp_seq=6 ttl=64 time=0.221 ms
64 bytes from borg.loc (10.1.1.10): icmp_seq=7 ttl=64 time=0.248 ms
64 bytes from borg.loc (10.1.1.10): icmp_seq=8 ttl=64 time=0.231 ms
64 bytes from borg.loc (10.1.1.10): icmp_seq=9 ttl=64 time=0.192 ms
64 bytes from borg.loc (10.1.1.10): icmp_seq=10 ttl=64 time=0.225 ms
64 bytes from borg.loc (10.1.1.10): icmp_seq=11 ttl=64 time=0.200 ms
64 bytes from borg.loc (10.1.1.10): icmp_seq=12 ttl=64 time=0.200 ms
^C
--- borg.loc ping statistics ---
12 packets transmitted, 12 received, 0% packet loss, time 11010ms
rtt min/avg/max/mdev = 0.167/0.210/0.254/0.025 ms
root@falcon:~# 
root@falcon:~# 
root@falcon:~# ping firewall.loc
PING firewall.loc (10.1.1.1) 56(84) bytes of data.
64 bytes from internet.firewall.loc (10.1.1.1): icmp_seq=1 ttl=64 time=0.239 ms
64 bytes from internet.firewall.loc (10.1.1.1): icmp_seq=2 ttl=64 time=0.340 ms
64 bytes from internet.firewall.loc (10.1.1.1): icmp_seq=3 ttl=64 time=0.334 ms
64 bytes from internet.firewall.loc (10.1.1.1): icmp_seq=4 ttl=64 time=0.349 ms
64 bytes from internet.firewall.loc (10.1.1.1): icmp_seq=5 ttl=64 time=0.238 ms
64 bytes from internet.firewall.loc (10.1.1.1): icmp_seq=6 ttl=64 time=0.351 ms
64 bytes from internet.firewall.loc (10.1.1.1): icmp_seq=7 ttl=64 time=0.319 ms
64 bytes from internet.firewall.loc (10.1.1.1): icmp_seq=8 ttl=64 time=0.314 ms
64 bytes from internet.firewall.loc (10.1.1.1): icmp_seq=9 ttl=64 time=0.353 ms
64 bytes from internet.firewall.loc (10.1.1.1): icmp_seq=10 ttl=64 time=0.157 ms
64 bytes from internet.firewall.loc (10.1.1.1): icmp_seq=11 ttl=64 time=0.137 ms
64 bytes from internet.firewall.loc (10.1.1.1): icmp_seq=12 ttl=64 time=0.223 ms
64 bytes from internet.firewall.loc (10.1.1.1): icmp_seq=13 ttl=64 time=0.259 ms
^C
--- firewall.loc ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12014ms
rtt min/avg/max/mdev = 0.137/0.277/0.353/0.075 ms
root@falcon:~# 
root@falcon:~# 
root@falcon:~# ping htpc.loc
PING htpc.loc (10.1.2.21) 56(84) bytes of data.
64 bytes from htpc.loc (10.1.2.21): icmp_seq=1 ttl=64 time=1.32 ms
64 bytes from htpc.loc (10.1.2.21): icmp_seq=2 ttl=64 time=0.825 ms
64 bytes from htpc.loc (10.1.2.21): icmp_seq=3 ttl=64 time=0.678 ms
64 bytes from htpc.loc (10.1.2.21): icmp_seq=4 ttl=64 time=0.792 ms
64 bytes from htpc.loc (10.1.2.21): icmp_seq=5 ttl=64 time=0.832 ms
64 bytes from htpc.loc (10.1.2.21): icmp_seq=6 ttl=64 time=0.811 ms
64 bytes from htpc.loc (10.1.2.21): icmp_seq=7 ttl=64 time=0.802 ms
64 bytes from htpc.loc (10.1.2.21): icmp_seq=8 ttl=64 time=0.797 ms
64 bytes from htpc.loc (10.1.2.21): icmp_seq=9 ttl=64 time=0.706 ms
64 bytes from htpc.loc (10.1.2.21): icmp_seq=10 ttl=64 time=0.701 ms
64 bytes from htpc.loc (10.1.2.21): icmp_seq=11 ttl=64 time=0.724 ms
^C
--- htpc.loc ping statistics ---
11 packets transmitted, 11 received, 0% packet loss, time 10017ms
rtt min/avg/max/mdev = 0.678/0.817/1.327/0.172 ms
root@falcon:~# 
root@falcon:~# 
root@falcon:~# ping sw1.n.loc
PING sw1.n.loc (10.1.4.2) 56(84) bytes of data.
64 bytes from sw1.n.loc (10.1.4.2): icmp_seq=1 ttl=64 time=3.41 ms
64 bytes from sw1.n.loc (10.1.4.2): icmp_seq=2 ttl=64 time=1.45 ms
64 bytes from sw1.n.loc (10.1.4.2): icmp_seq=3 ttl=64 time=1.45 ms
64 bytes from sw1.n.loc (10.1.4.2): icmp_seq=4 ttl=64 time=1.52 ms
64 bytes from sw1.n.loc (10.1.4.2): icmp_seq=5 ttl=64 time=1.54 ms
64 bytes from sw1.n.loc (10.1.4.2): icmp_seq=6 ttl=64 time=1.52 ms
64 bytes from sw1.n.loc (10.1.4.2): icmp_seq=7 ttl=64 time=1.40 ms
64 bytes from sw1.n.loc (10.1.4.2): icmp_seq=8 ttl=64 time=1.46 ms
64 bytes from sw1.n.loc (10.1.4.2): icmp_seq=9 ttl=64 time=1.54 ms
^C
--- sw1.n.loc ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8011ms
rtt min/avg/max/mdev = 1.404/1.702/3.416/0.609 ms
root@falcon:~#

Oddly my switch gives a pretty crappy ping, though I think that's just the management and should not affect actual traffic going through it.

 

[Midwayman]

I dont' think its possible to beat this. Well ping anyways.

 

[Krazy4Real]

I dont' think its possible to beat this. Well ping anyways.

Wow... puts me to shame for sure.