Quote:
Originally Posted by Florence
Cant understand why BT customers have so many hops to get to google it is almost as if BT don't want them to arrive at google or they don't know how to do a fast network
|
Geographic location?
How do you get
www.l.google.com to resolve as any IP other than 216.239.59.103?
Anyway...
I'm on ADSL24 (Entanet Reseller)
Tracing route to nf-in-f99.google.com [64.233.183.99]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms mygateway.ar7 [192.168.1.1]
2 32 ms 32 ms 32 ms ironwood.dsl.enta.net [87.127.229.6]
3 32 ms 32 ms 33 ms vlan4002.telehouse-east.dsl.enta.net [87.127.229.1]
4 31 ms 32 ms 31 ms te5-2.telehouse-east.core.enta.net [62.249.192.121]
5 32 ms 31 ms 32 ms te4-3.global-switch.core.enta.net [87.127.236.82]
6 32 ms 32 ms 32 ms te4-3.telehouse-north.core.enta.net [87.127.236.41]
7 32 ms 30 ms 31 ms 72.14.198.46
8 31 ms 31 ms 32 ms 209.85.252.42
9 51 ms 51 ms 52 ms 216.239.43.123
10 52 ms 53 ms 52 ms 72.14.233.77
11 66 ms 63 ms 62 ms 216.239.43.34
12 56 ms 51 ms 50 ms nf-in-f99.google.com [64.233.183.99]
Trace complete.
Norfolk - no not the one in Virginia...
EDIT: Just looked a few pages back at your trace Florence - virtually the same as mine (on Entanet)