Re: cable modem connection slower than dial up
Rodrigo Paes <email@example.com> writes:
> "schmity" <firstname.lastname@example.org> wrote:
>> brent@Linuxbox:~$ ping www.google.com
>> PING www.l.google.com (126.96.36.199) 56(84) bytes of data.
>> 64 bytes from 188.8.131.52: icmp_seq=1 ttl=241 time=78.5 ms
>> 64 bytes from 184.108.40.206: icmp_seq=2 ttl=241 time=61.2 ms
> that's actually pretty good time... check out min :)
> PING www.l.google.com (220.127.116.11) 56(84) bytes of data.
> 64 bytes from 18.104.22.168: icmp_seq=1 ttl=244 time=715 ms
> 64 bytes from 22.214.171.124: icmp_seq=2 ttl=244 time=709 ms
I was shocked to see:
PING www.l.google.com (126.96.36.199): 56 data bytes
64 bytes from 188.8.131.52: icmp_seq=0 ttl=243 time=15.3 ms
64 bytes from 184.108.40.206: icmp_seq=1 ttl=243 time=16.6 ms
64 bytes from 220.127.116.11: icmp_seq=2 ttl=243 time=16.7 ms
64 bytes from 18.104.22.168: icmp_seq=3 ttl=243 time=16.5 ms
Man the internet is faster than I remember...
Google, or somebody, is apparently doing something clever, because
according to traceroute[*], not only is there an unsually low number of
hops to the above google machine ("only" 11), but it's located in Japan
(where I am), avoiding the big trans-pacific delay (~100ms, generally)
that I get with most U.S. sites.
[*] Actually "mtr -t", a very nice traceroute replacement.
`Suppose Korea goes to the World Cup final against Japan and wins,' Moon said.
`All the past could be forgiven.' [NYT]