| [Connectivity] Tracrt reveals I go through Europe Tracing route to etf.spaz.com [66.135.105.42]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 6 ms 8 ms 9 ms 10.217.9.1
3 8 ms 7 ms 9 ms 68.87.158.45
4 8 ms 6 ms 7 ms 10g-9-1-ur01.boston.ma.boston.comcast.net [68.87
.145.49]
5 8 ms 6 ms 8 ms 68.87.144.57
6 8 ms 10 ms 10 ms 10g-8-3-ar01.needham.ma.boston.comcast.net [68.8
7.144.53]
7 8 ms 33 ms 10 ms 12.118.88.5
8 25 ms 26 ms 16 ms tbr1-p012801.cb1ma.ip.att.net [12.123.40.210]
9 16 ms 16 ms 16 ms tbr2-cl1.n54ny.ip.att.net [12.122.10.22]
10 17 ms 15 ms 15 ms ggr2-p390.n54ny.ip.att.net [12.123.3.62]
11 19 ms 24 ms 15 ms att-gw.nyc.dtag.de [192.205.32.58]
12 72 ms 25 ms 23 ms 217.239.40.78
13 86 ms 89 ms 89 ms 38.112.93.50
14 89 ms 90 ms 88 ms Emerald.NetSurf.Net [66.135.108.130]
15 * * * Request timed out.
16 85 ms 84 ms 82 ms www.spaz.com [66.135.105.42]
Trace complete.
Any idea why and if there is anything I can do about it?
Thanks,
Tim |
|
| Re: [Connectivity] Tracrt reveals I go through Eur Domain names are not always directly related to location. a whois of the IP shows it located in florida.
OrgName: AT&T Bell Laboratories
OrgID: ATT
Address: 3200 Lake Emma Road
City: Lake Mary
StateProv: FL
PostalCode: 32746
Country: US
NetRange: 192.205.0.0 - 192.205.255.255
CIDR: 192.205.0.0/16
NetName: NETBLK-ATT
NetHandle: NET-192-205-0-0-1
Parent: NET-192-0-0-0-0
NetType: Direct Allocation
NameServer: OHCU.OH.MT.NP.ELS-GMS.ATT.NET
NameServer: WYCU.WY.BR.NP.ELS-GMS.ATT.NET
NameServer: MACU.MA.MT.NP.ELS-GMS.ATT.NET
Comment:
RegDate: 1992-08-03
Updated: 1997-11-04
TechHandle: JD2290-ARIN
TechName: Davis, John
TechPhone: +1-513-352-7285
TechEmail: jdavis@dcsdcpmx.attmail.com
OrgTechHandle: IAA8-ARIN
OrgTechName: IP Address Administrator
OrgTechPhone: +1-407-805-7323
OrgTechEmail: lperkins@att.com |
|
| Hmm...
When I try to get info on 217.239.40.78, I am told:
inetnum: 217.239.37.0 - 217.239.41.255
netname: DTAG-INT1
descr: Deutsche Telekom AG, Internet Service Provider
country: DE
admin-c: WS425-RIPE
tech-c: DTST
status: ASSIGNED PA
remarks: ************************************************************
remarks: * ABUSE CONTACT: *****@t-ipnet.de IN CASE OF HACK ATTACKS, *
remarks: * ILLEGAL ACTIVITY, VIOLATION, SCANS, PROBES, SPAM, ETC. *
remarks: ************************************************************
mnt-by: DTAG-NIC
changed: *********@telekom.de 20030211
source: RIPE
person: WN-IPC-IIC Stuttgart
address: Deutsche Telekom AG
address: Deckerstr.35
address: 70372 Stuttgart
e-mail: ********************@Telekom.de
phone: +49 711 270 2814
fax-no: +49 711 270 2829
mnt-by: DTAG-NIC
nic-hdl: WS425-RIPE
notify: *******@nic.telekom.de
notify: ***@nic.dtag.de
mnt-by: DTAG-NIC
changed: *******@nic.telekom.de 20020415
source: RIPE
person: Security Team
address: Deutsche Telekom AG
address: Germany
phone: +49 180 5334332
fax-no: +49 180 5334252
e-mail: *****@t-ipnet.de
nic-hdl: DTST
mnt-by: DTAG-NIC
changed: *****@t-ipnet.de 20030210
source: RIPE
% Information related to '217.224.0.0/11AS3320'
route: 217.224.0.0/11
descr: Deutsche Telekom AG, Internet service provider
origin: AS3320
member-of: AS3320:RS-PA-TELEKOM
mnt-by: DTAG-RR
changed: **@nic.dtag.de 20010405
source: RIPE
changed: **@TE142.T-COM.XX 20040615
So that particular IP is in Germany, but I see how att-gw.nyc.dtag.de is not. |
|
 scoobyPremium
join:2001-05-01
Schaumburg, IL
kudos:1
1 edit | reply to timisdaman
You sure do goto Germany. I wonder was something broke on the net when you did that traceroute or if it is always like that for you. |
|
| I did that traceroute 10/10/2005. I noticed it because I play a game on that server, and my ping was unusually high. It was not always like this. I first noticed it last week. No idea what happened. |
|
| reply to timisdaman
here it is. found it. the one right after the german router:
38.112.93.50
Performance Systems International Inc. COGENT-NB-0002 (NET-38-112-0-0-1)
38.112.0.0 - 38.119.255.255
this is most likely a side effect of poor crisis management when level3 cut off cogent. they most likely routed through germany in order to keep their servers online. |
|
| heh, i'm lost... what do you mean "when level3 cut off cogent"?
thanks to everyone for the replies, btw  |
|
scoobyPremium
join:2001-05-01
Schaumburg, IL
kudos:1 | reply to timisdaman
Yeah spaz.com is hosted on Cogent. Most likely AT&T is being a bully to them. If you know the admin, they should be able to get cogent to address the issue. Most likely that is the closest point of peering between Cogent and AT&T so the traffic goes there.
This is one of the big negatives Comcast has by being single homed to AT&T. If they had a connection to Cogent (or any of the Cogent friendly providers) in your area you'd have killer ping times to that server. Hopefully this will change with SBC buying AT&T. |
|
| Thanks for the info. I've managed to get around this by connecting to my school's (Boston University) VPN. I actually get better pings with VPN than before this problem. This is weird for me, as in my previous experience with VPN (Boston College), my connection was much slower. |
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
 ·SONIC.NET
·Pacific Bell - SBC
2 edits | reply to timisdaman
said by timisdaman:Tracing route to etf.spaz.com [66.135.105.42] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.1.1 2 6 ms 8 ms 9 ms 10.217.9.1 3 8 ms 7 ms 9 ms 68.87.158.45 4 8 ms 6 ms 7 ms 10g-9-1-ur01.boston.ma.boston.comcast.net [68.87 .145.49] 5 8 ms 6 ms 8 ms 68.87.144.57 6 8 ms 10 ms 10 ms 10g-8-3-ar01.needham.ma.boston.comcast.net [68.8 7.144.53] 7 8 ms 33 ms 10 ms 12.118.88.5 8 25 ms 26 ms 16 ms tbr1-p012801.cb1ma.ip.att.net [12.123.40.210] 9 16 ms 16 ms 16 ms tbr2-cl1.n54ny.ip.att.net [12.122.10.22] 10 17 ms 15 ms 15 ms ggr2-p390.n54ny.ip.att.net [12.123.3.62] 11 19 ms 24 ms 15 ms att-gw. nyc.dtag.de [192.205.32.58] 12 72 ms 25 ms 23 ms 217.239.40.78 13 86 ms 89 ms 89 ms 38.112.93.50 14 89 ms 90 ms 88 ms Emerald.NetSurf.Net [66.135.108.130] 15 * * * Request timed out. 16 85 ms 84 ms 82 ms www.spaz.com [66.135.105.42] Trace complete. Any idea why and if there is anything I can do about it? Thanks, Tim Tracert from me to you:
10/10/05 23:30:10 Slow traceroute 68.87.158.45
Trace 68.87.158.45 ...
192.168.102.1 RTT: 0ms TTL: 64 (Chihiro ok)
192.168.0.1 RTT: 41ms TTL:170 (Suzuka ok)
71.131.223.254 RTT: 55ms TTL:170 (adsl-71-131-223-254.dsl.sntc01.pacbell.net ok)
63.203.51.65 RTT: 42ms TTL:170 (dist1-vlan60.sntc01.pbi.net ok)
64.161.1.145 RTT: 41ms TTL:170 (bb1-g8-0-1.sntcca.sbcglobal.net ok)
151.164.40.166 RTT: 55ms TTL:170 (bb2-p9-0.sntc01.sbcglobal.net ok)
151.164.241.201 RTT: 41ms TTL:170 (core2-p6-3.crscca.sbcglobal.net ok)
151.164.40.62 RTT: 55ms TTL:170 (bb1-p8-0.crscca.sbcglobal.net ok)
151.164.41.109 RTT: 55ms TTL:170 (ex2-p5-0.eqsjca.sbcglobal.net ok)
151.164.191.201 RTT: 68ms TTL:170 (ex1-p9-0.eqsjca.sbcglobal.net ok)
144.223.242.81 RTT: 55ms TTL:170 (sl-st20-sj-0-0.sprintlink.net ok)
144.232.9.67 RTT: 55ms TTL:170 (sl-st21-sj-1-0.sprintlink.net ok)
144.232.9.206 RTT: 55ms TTL:170 (No rDNS)
* 12.122.80.58 RTT: 110ms TTL:170 (tbr2-p011901.sffca.ip.att.net bogus rDNS:
host not found [authoritative])
12.122.10.41 RTT: 96ms TTL:170 (tbr1-cl2.sl9mo.ip.att.net bogus rDNS:
host not found [authoritative])
12.122.9.142 RTT: 110ms TTL:170 (tbr2-cl2.sl9mo.ip.att.net bogus rDNS:
host not found [authoritative])
12.122.10.45 RTT: 96ms TTL:170 (tbr2-cl7.cgcil.ip.att.net bogus rDNS:
host not found [authoritative])
12.122.10.105 RTT: 96ms TTL:170 (tbr2-cl5.cb1ma.ip.att.net bogus rDNS:
host not found [authoritative])
12.122.81.13 RTT: 110ms TTL:170 (gar13-p390.cb1ma.ip.att.net bogus rDNS:
host not found [authoritative])
12.118.88.10 RTT: 96ms TTL:170 (No rDNS)
68.87.145.145 RTT: 96ms TTL:170 (10g-8-1-ar02.needham.ma.boston.comcast.net ok)
68.87.145.133 RTT: 96ms TTL:170 (10g-9-1-ar01.needham.ma.boston.comcast.net ok)
68.87.144.54 RTT: 96ms TTL:170 (10g-9-1-ur01.brookline.ma.boston.comcast.net ok)
68.87.144.58 RTT: 110ms TTL:170 (10g-8-3-ur01.boston.ma.boston.comcast.net ok)
68.87.158.45 RTT: 96ms TTL:231 (No rDNS)
Now, a Sam Spade "Slow traceroute" from Santa Clara, Calif. to "etf.spaz.com":
10/10/05 23:43:02 Slow traceroute etf.spaz.com
Trace etf.spaz.com (66.135.105.42) ...
192.168.102.1 RTT: 0ms TTL: 64 (Chihiro ok)
192.168.0.1 RTT: 14ms TTL:170 (Suzuka ok)
71.131.223.254 RTT: 27ms TTL:170 (adsl-71-131-223-254.dsl.sntc01.pacbell.net ok)
63.203.51.65 RTT: 14ms TTL:170 (dist1-vlan60.sntc01.pbi.net ok)
64.161.1.129 RTT: 41ms TTL:170 (bb1-g1-0-1.sntcca.sbcglobal.net ok)
151.164.40.166 RTT: 14ms TTL:170 (bb2-p9-0.sntc01.sbcglobal.net ok)
151.164.241.193 RTT: 13ms TTL:170 (core2-p6-1.crscca.sbcglobal.net ok)
151.164.40.58 RTT: 27ms TTL:170 (bb1-p1-0.crscca.sbcglobal.net ok)
151.164.41.109 RTT: 41ms TTL:170 (ex2-p5-0.eqsjca.sbcglobal.net ok)
151.164.249.186 RTT: 27ms TTL:170 (asn174-cogent.eqsjca.sbcglobal.net ok)
66.28.4.134 RTT: 28ms TTL:170 (p5-0.core02.sfo01.atlas.cogentco.com bogus rDNS:
host not found [authoritative])
66.28.4.69 RTT: 28ms TTL:170 (p15-0.core01.sfo01.atlas.cogentco.com bogus rDNS:
host not found [authoritative])
66.28.4.186 RTT: 68ms TTL:170 (p14-0.core01.ord01.atlas.cogentco.com bogus rDNS:
host not found [authoritative])
66.28.4.62 RTT: 83ms TTL:170 (p15-0.core02.ord01.atlas.cogentco.com bogus rDNS:
host not found [authoritative])
66.28.4.214 RTT: 82ms TTL:170 (p5-0.core01.yyz01.atlas.cogentco.com bogus rDNS:
host not found [authoritative])
38.112.37.50 RTT: 96ms TTL:170 (vl102.na01.b011027-1.yyz01.atlas.cogentco.com bogus
rDNS: host not found [authoritative])
38.112.93.50 RTT: 83ms TTL:170 (No rDNS)
66.135.108.130 RTT: 96ms TTL:170 (Emerald.NetSurf.Net ok)
* * * failed
66.135.105.42 RTT: 96ms TTL:105 (www.spaz.com ok)
I expect that "att-gw.nyc.dtag.de" is located somewhere on the east coast of the U.S.A.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
| I agree with NormanS. There is no possibility that the IP in question is anywhere other than the east coast. Since the minimum observed ping from your location is 15 ms, it has to be within 1,000 miles assuming that there are no delays in any router. Looking at the latencies for earlier hops, it sure looks to be in NYC just like its URL suggests. |
|
|
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| reply to timisdaman
said by timisdaman:Hmm... When I try to get info on 217.239.40.78, I am told: inetnum: 217.239.37.0 - 217.239.41.255 netname: DTAG-INT1 descr: Deutsche Telekom AG, Internet Service Provider country: DE "Whois" inforation tells you who owns a given IP address. It does not tell you where a given IP address is actually located. With overseas peering arrangements it is entirely possible for any given router to "belong" to one country, yet be located in another country. Consider the following trace route:
10/11/05 07:33:17 Slow traceroute 60.10.106.228
Trace 60.10.106.228 ...
192.168.102.1 RTT: 0ms TTL: 64 (Chihiro ok)
192.168.0.1 RTT: 0ms TTL:170 (Suzuka ok)
71.131.223.254 RTT: 14ms TTL:170 (adsl-71-131-223-254.dsl.sntc01.pacbell.net ok)
63.203.35.66 RTT: 14ms TTL:170 (dist2-vlan50.sntc01.pbi.net ok)
64.161.1.145 RTT: 27ms TTL:170 (bb1-g8-0-1.sntcca.sbcglobal.net ok)
151.164.40.170 RTT: 14ms TTL:170 (bb2-p6-0.sntc01.sbcglobal.net ok)
151.164.241.201 RTT: 13ms TTL:170 (core2-p6-3.crscca.sbcglobal.net ok)
151.164.40.58 RTT: 28ms TTL:170 (bb1-p1-0.crscca.sbcglobal.net ok)
151.164.41.109 RTT: 14ms TTL:170 (ex2-p5-0.eqsjca.sbcglobal.net ok)
151.164.191.201 RTT: 27ms TTL:170 (ex1-p9-0.eqsjca.sbcglobal.net ok)
144.223.242.81 RTT: 14ms TTL:170 (sl-st20-sj-0-0.sprintlink.net ok)
144.232.20.62 RTT: 41ms TTL:170 (sl-bb25-sj-10-0.sprintlink.net ok)
144.232.9.32 RTT: 28ms TTL:170 (sl-bb23-ana-4-0.sprintlink.net ok)
144.232.1.154 RTT: 28ms TTL:170 (sl-gw23-ana-10-0.sprintlink.net ok)
160.81.205.194 RTT: 219ms TTL:170 (sl-chinnet-2-0.sprintlink.net ok)
219.158.3.13 RTT: 260ms TTL:170 (No rDNS)
219.158.4.30 RTT: 303ms TTL:170 (No rDNS)
219.158.8.230 RTT: 329ms TTL:170 (No rDNS)
202.99.160.254 RTT: 275ms TTL:170 (No rDNS)
61.182.174.98 RTT: 274ms TTL:170 (No rDNS)
218.12.255.202 RTT: 275ms TTL:170 (No rDNS)
* * * failed
60.10.106.228 RTT: 385ms TTL:106 (No rDNS)
10/11/05 07:33:34 IP Block 160.81.205.194
Trying 160.81.205.194 at ARIN
Trying 160.81.205 at ARIN
OrgName: Sprint
OrgID: SPRN
Address: 12502 Sunrise Valley Drive
City: Reston
StateProv: VA
PostalCode: 20196
Country: US
NetRange: 160.81.0.0 - 160.81.255.255
CIDR: 160.81.0.0/16
NetName: SPRN-BLKI
NetHandle: NET-160-81-0-0-1
Parent: NET-160-0-0-0-0
NetType: Direct Allocation
NameServer: NS1-AUTH.SPRINTLINK.NET
NameServer: NS2-AUTH.SPRINTLINK.NET
NameServer: NS3-AUTH.SPRINTLINK.NET
Comment:
RegDate: 1992-04-28
Updated: 2005-03-02
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
| att-gw.nyc.dtag.de [192.205.32.58] is in washington DC, I believe,
but 217.239.40.78 is in Germany. |
|
1 edit | reply to timisdaman
|
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
1 edit | reply to timisdaman
Not according to the ping times. You have 25ms to 217.239.40.78, but you have 89ms to 38.112.93.50. What law of physics permits electrons to pass though a trans-Atlantic cable in less time that to pass through wire/fiber along the U.S. east coast?
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
| reply to timisdaman
Re: [Connectivity] Tracrt reveals I go through Europe umm guys do you understand how fast light travels? Germany is not far from the US at all. Ping time are mostly made up from equipment, not distance.
think about this. You can ping California from New York in 20 ms (I'm saying 20 because that's what I was getting in New York to some servers in Sandiago). How how can you say that germany would require at least 200ms? It's not 10 the distance.
I'm GUESSING it wouldn't take more than 20 to 50 ms to cross the atlantic on fiber. That even sounds high, but I don't know.
Do the math though it should be simple. I don't feel like putting the thought into formulating it. |
|
| The math is simple. 15 ms per 1000 miles of fiber. The minimum ping for a path between NY and CA is typically 80 ms, of which ~50 ms comes from the distance. NY to the continent is typicallly 200 ms. |
|
 dadkinsCan you do Blu?Premium,MVM
join:2003-09-26
Hercules, CA
kudos:18
1 edit | reply to timisdaman
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\David Adkins>tracert etf.spaz.com
Tracing route to etf.spaz.com [66.135.105.42]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 12 ms 9 ms 44 ms 68.87.196.249
4 15 ms 9 ms 9 ms 68.87.192.97
5 12 ms 29 ms 11 ms 68.87.192.93
6 44 ms 11 ms 9 ms 68.87.195.58
7 14 ms 28 ms 21 ms 12.127.32.33
8 16 ms 35 ms 16 ms tbr2-p013701.sffca.ip.att.net [12.123.13.177]
9 12 ms 14 ms 16 ms 12.122.81.137
10 15 ms 12 ms 14 ms p5-0.core01.sjc03.atlas.cogentco.com [154.54.11.
237]
11 17 ms 16 ms 15 ms p5-0.core02.sfo01.atlas.cogentco.com [66.28.4.13
4]
12 18 ms 20 ms 14 ms p15-0.core01.sfo01.atlas.cogentco.com [66.28.4.6
9]
13 61 ms 80 ms 61 ms p14-0.core01.ord01.atlas.cogentco.com [66.28.4.1
86]
14 59 ms 61 ms 74 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4.6
2]
15 75 ms 75 ms 74 ms p5-0.core01.yyz01.atlas.cogentco.com [66.28.4.21
4]
16 78 ms 78 ms 79 ms vl102.na01.b011027-1.yyz01.atlas.cogentco.com [3
8.112.37.50]
17 75 ms 76 ms 76 ms 38.112.93.51
18 78 ms 76 ms 93 ms Emerald.NetSurf.Net [66.135.108.130]
19 * * * Request timed out.
20 79 ms 76 ms 80 ms www.spaz.com [66.135.105.42]
Trace complete.
C:\Documents and Settings\David Adkins>
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\David Adkins>tracert www.pipex.net
Tracing route to www.pipex.net [62.241.160.129]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 63 ms 10 ms 26 ms 68.87.196.249
4 9 ms 9 ms 9 ms 68.87.192.97
5 14 ms 30 ms 31 ms 68.87.192.93
6 16 ms 13 ms 12 ms 68.87.195.62
7 12 ms 50 ms 32 ms 12.117.240.17
8 15 ms 17 ms 31 ms tbr2032701.sffca.ip.att.net [12.122.82.2]
9 12 ms 55 ms 56 ms ggr2-p390.sffca.ip.att.net [12.123.13.194]
10 15 ms 13 ms 14 ms att-gw.ashburn.eli.net [192.205.32.74]
11 15 ms 14 ms 14 ms 0.so-2-0-0.XL2.SCL2.ALTER.NET [152.63.57.102]
12 18 ms 14 ms 14 ms 0.so-3-0-0.TL2.SCL2.ALTER.NET [152.63.48.93]
13 77 ms 76 ms 80 ms 0.so-7-0-0.IL2.DCA6.ALTER.NET [152.63.9.221]
14 75 ms 77 ms 108 ms so-1-0-0.IR2.DCA4.ALTER.NET [146.188.13.46]
15 170 ms 150 ms 153 ms 0.so-5-0-0.TR2.LND9.ALTER.NET [146.188.8.174]
16 157 ms 156 ms 155 ms so-6-0-0.XR1.LND9.ALTER.NET [146.188.15.42]
17 153 ms 153 ms 192 ms pos1-0.gw2.LND9.ALTER.net [158.43.150.158]
18 151 ms 154 ms 171 ms PIPEX-gw3.customer.ALTER.NET [146.188.56.98]
19 156 ms 174 ms 155 ms darkstar.systems.pipex.net [62.241.160.129]
Trace complete.
C:\Documents and Settings\David Adkins>
#1 is to the server you are tracing(80ms).
#2 is to Pipex.net(UK ISP)
I'm in California, no way I can hit the UK(or Europe) at under 150ms(today is a "Good Day").
--
Think outside the Fox... Opera |
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| reply to dhgdfg
Re: [Connectivity] Tracrt reveals I go through Eursaid by dhgdfg :
umm guys do you understand how fast light travels? 186,000 miles per second in fiber? I don't think so. Look up "index of refraction". In any case, if that were the primary factor behind latency, there would be no difference between the latency of dial-up and HSI traceroutes. But Sam Spade tells an interesting "Tale of Two Traceroutes":
10/11/05 21:40:06 Slow traceroute 217.239.40.78
Trace 217.239.40.78 ...
192.168.102.3 RTT: 14ms TTL:170 (Shizuku ok)
209.244.43.71 RTT: 192ms TTL:170 (nas7.SanJose1.Level3.net ok)
63.215.14.3 RTT: 192ms TTL:170 (ge-7-0-1.core2.SanJose1.Level3.net ok)
4.68.123.33 RTT: 192ms TTL:170 (ae-1-52.bbr2.SanJose1.Level3.net ok)
64.159.0.217 RTT: 206ms TTL:170 (as-0-0.mp2.SanFrancisco1.Level3.net ok)
4.68.124.206 RTT: 192ms TTL:170 (ge-6-0-0.gar1.SanFrancisco1.Level3.net ok)
4.68.111.54 RTT: 192ms TTL:170 (No rDNS)
62.154.5.201 RTT: 302ms TTL:170 (yto-sa1.YTO.CA.net.DTAG.DE ok)
217.239.40.78 RTT: 289ms TTL:245 (No rDNS)
10/11/05 21:41:15 Slow traceroute 217.239.40.78
Trace 217.239.40.78 ...
192.168.102.1 RTT: 0ms TTL: 64 (Chihiro ok)
192.168.0.1 RTT: 14ms TTL:170 (Suzuka ok)
71.131.223.254 RTT: 41ms TTL:170 (adsl-71-131-223-254.dsl.sntc01.pacbell.net ok)
63.203.35.65 RTT: 13ms TTL:170 (dist1-vlan50.sntc01.pbi.net ok)
64.161.1.129 RTT: 28ms TTL:170 (bb1-g1-0-1.sntcca.sbcglobal.net ok)
151.164.40.166 RTT: 27ms TTL:170 (bb2-p9-0.sntc01.sbcglobal.net ok)
151.164.241.201 RTT: 14ms TTL:170 (core2-p6-3.crscca.sbcglobal.net ok)
151.164.242.82 RTT: 41ms TTL:170 (core1-p11-0.cranca.sbcglobal.net ok)
151.164.40.90 RTT: 41ms TTL:170 (bb1-p1-0.cranca.sbcglobal.net ok)
151.164.41.29 RTT: 41ms TTL:170 (ex1-p15-0.eqlaca.sbcglobal.net ok)
151.164.40.162 RTT: 41ms TTL:170 (ex2-p9-0.eqlaca.sbcglobal.net ok)
151.164.248.194 RTT: 69ms TTL:170 (No rDNS)
217.239.40.17 RTT: 41ms TTL:170 (No rDNS)
62.154.5.201 RTT: 110ms TTL:170 (yto-sa1.YTO.CA.net.DTAG.DE ok)
217.239.40.78 RTT: 110ms TTL:234 (No rDNS)
P.S. I have to brag a little about figuring out how to manage Internet connectivity through two different routers on the same LAN segment. ;)
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
| reply to timisdaman
Re: [Connectivity] Tracrt reveals I go through Europe "In any case, if that were the primary factor behind latency, there would be no difference between the latency of dial-up and HSI traceroutes"
no you are wrong with that one |
|
