justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
 ·AT&T Midwest
·AT&T Yahoo
| Where does your 6to4 relay address (192.88.99.1) go?
»tools.ietf.org/html/rfc3068
Post your provider and a traceroute to 192.88.99.1.
If that host actually works as a 6to4 relay, please say so too.
Thanks!
AT+T DSL & T1s in Illinois... route to Switzerland
# traceroute 192.88.99.1
traceroute to 192.88.99.1 (192.88.99.1), 64 hops max, 40 byte packets
2 adsl-68-75-183-254.dsl.emhril.ameritech.net (68.75.183.254) 10.428 ms 9.939 ms 10.590 ms
3 dist2-vlan60.emhril.ameritech.net (68.22.72.131) 11.433 ms 15.447 ms 10.747 ms
4 bb2-g10-0.emhril.ameritech.net (151.164.43.84) 46.896 ms 158.818 ms 46.747 ms
5 ex2-p5-0.eqchil.sbcglobal.net (151.164.42.139) 178.486 ms 136.200 ms 40.540 ms
6 asn3549-glbx.eqchil.sbcglobal.net (151.164.248.18) 12.123 ms 11.931 ms 11.626 ms
7 swice2-switch-ch.so-0-1-0.ar2.cdg2.gblx.net (64.212.70.62) 118.182 ms 117.469 ms 118.720 ms
8 swi6netce1-g0-0.switch.ch (130.59.35.137) 126.130 ms * 126.133 ms |
|
justin236
@qwest.net
| Our isp (at home) is hevanet (Portland, OR).
traceroute to 192.88.99.1 (192.88.99.1), 30 hops max, 40 byte packets
1 [our home nat box] 1.592 ms 1.693 ms 0.296 ms
2 c3-dsl.hevanet.com (130.94.162.1) 68.349 ms 65.417 ms 73.107 ms
3 gw.hevanet.com (198.5.254.254) 58.800 ms 60.065 ms 57.872 ms
4 cogentco-gw1.hevanet.com (157.238.155.97) 56.844 ms 57.286 ms 57.740 ms
5 g3-1.core01.pdx01.atlas.cogentco.com (38.112.37.217) 57.793 ms 58.312 ms 56.943 ms
6 p2-0.core01.smf01.atlas.cogentco.com (154.54.3.125) 67.655 ms 69.351 ms 71.308 ms
7 * p15-0.core01.den01.atlas.cogentco.com (66.28.4.129) 90.391 ms 91.603 ms
8 p5-0.core01.mci01.atlas.cogentco.com (66.28.4.30) 101.625 ms 101.157 ms 100.906 ms
9 p5-0.core02.ord01.atlas.cogentco.com (66.28.4.34) 213.072 ms 211.350 ms 210.709 ms
10 p15-0.core01.ord01.atlas.cogentco.com (66.28.4.61) 371.967 ms 261.003 ms 258.121 ms
11 p14-0.core01.alb02.atlas.cogentco.com (154.54.1.57) 215.029 ms 214.728 ms 214.006 ms
12 p14-0.core01.bos01.atlas.cogentco.com (66.28.4.109) 214.704 ms 215.160 ms 215.056 ms
13 t3-3.mpd01.bos01.atlas.cogentco.com (154.54.5.22) 212.076 ms 209.796 ms 211.280 ms
14 t2-3.mpd03.jfk02.atlas.cogentco.com (154.54.6.10) 141.094 ms 140.129 ms 140.332 ms
15 t2-2.mpd02.lon01.atlas.cogentco.com (66.28.4.42) 211.334 ms 210.056 ms 210.125 ms
16 p3-2.mpd01.ams03.atlas.cogentco.com (130.117.1.169) 218.018 ms 220.235 ms 218.802 ms
17 t7-2.mpd01.fra03.atlas.cogentco.com (130.117.1.161) 344.265 ms 337.235 ms 422.261 ms
18 decix2.rm-com.net (80.81.193.23) 230.985 ms 230.206 ms 230.683 ms
19 ipv6gw00-cc1.rm-com.net (217.173.143.232) 238.944 ms 236.553 ms *
That's so far away, I wouldn't even consider trying to tunnel through it. Our upstream connectivity from hevanet is horrible. Why does it take a dozen cogentco routers to decide what to do with a packet? |
|
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL | Wow!
Portland, OR
Sacramento, CA
Denver, CO
Kansas City
Chicago, IL (ORD)
Albany, NY
Boston, NY
JFK, New York, NY
London, England
Amsterdam
France! |
|
justin236
@qwest.net
| This is coming from 71.216.22.6 ...
traceroute to 192.88.99.1 (192.88.99.1), 30 hops max, 52 byte packets
1 [local nat box] 0.125 ms 0.197 ms 0.086 ms
2 ptld-dsl-gw11-203.ptld.qwest.net (207.225.84.203) 39.291 ms 39.286 ms 38.867 ms
3 ptld-agw1.inet.qwest.net (207.225.85.81) 39.424 ms 38.634 ms 39.117 ms
4 por-core-01.inet.qwest.net (205.171.130.65) 39.393 ms * 39.891 ms
5 sea-core-02.inet.qwest.net (67.14.32.18) 43.299 ms 43.809 ms 43.580 ms
6 sea-brdr-01.inet.qwest.net (205.171.26.58) 43.314 ms 43.033 ms 43.826 ms
7 sl-bb21-sea-3-0.sprintlink.net (144.232.9.113) 43.091 ms 43.279 ms 43.825 ms
8 sl-bb1v6-sea-8-0-0.sprintlink.net (144.232.6.38) 44.072 ms * 43.972 ms
Qwest.net looks a little better. Terminates after only 7 hops past the nat box. Good response times, too. Stays out of that cogentco quagmire.
How do you hook up to one of these 192.88.99.1 thingies anyways? |
|
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
·AT&T Yahoo
| 192.88.99.1 is the 6 to 4 relay anycast address. ISPs should ideally configure their BGP routers to choose the closest 6 to 4 relay peer. If the ISP doesn't care, it seems like most people wind up getting sent to Europe.
Got a Linksys router with DD-WRT?
»www.dd-wrt.com/wiki/index.php/IPv6
Or a Linksys with OpenWRT?
»wiki.openwrt.org/IPv6_howto
Mac OS X?
»www.cs.utk.edu/~moore/hints/howt···osx.html
Windows?
Google for it. Lots of info out there. |
|
Deep Dish
join:2006-08-17
Canada
 ·Rogers Portable In..
| reply to justbits
Primus Business DSL in Toronto..
traceroute to 192.88.99.1 (192.88.99.1), 30 hops max, 40 byte packets
1 ** nat ** 1.506 ms 1.316 ms 1.263 ms
2 lo-0.erx.tor.primus.ca (216.254.132.30) 10.516 ms 39.305 ms 24.272 ms
3 core2.tor.primus.ca (216.254.130.165) 9.341 ms 9.588 ms 9.762 ms
4 gi1-1-202.bb1.tor.primus.ca (216.254.129.164) 10.338 ms 10.277 ms 10.019 ms
5 g2-5.mpd01.yyz02.atlas.cogentco.com (38.112.1.5) 10.343 ms 10.216 ms 12.889 ms
6 v3493.mpd01.yyz01.atlas.cogentco.com (154.54.5.85) 9.899 ms 10.058 ms 10.482 ms
7 g3-0-0-3491.core01.yyz01.atlas.cogentco.com (154.54.5.77) 10.679 ms 10.300 ms 10.095 ms
8 p4-0.core01.alb02.atlas.cogentco.com (66.28.4.217) 17.595 ms 19.274 ms 18.244 ms
9 p14-0.core01.bos01.atlas.cogentco.com (66.28.4.109) 21.401 ms 21.115 ms 21.596 ms
10 p3-0.core01.lon01.atlas.cogentco.com (130.117.0.45) 91.620 ms 92.573 ms 92.310 ms
11 p15-0.core01.ams03.atlas.cogentco.com (130.117.1.226) 99.767 ms 99.895 ms 100.468 ms
12 t3-2.mpd01.ams03.atlas.cogentco.com (130.117.0.238) 100.758 ms 100.995 ms 100.658 ms
13 t7-2.mpd01.fra03.atlas.cogentco.com (130.117.1.161) 118.728 ms 107.385 ms 107.136 ms
14 decix2.rm-com.net (80.81.193.23) 107.818 ms 107.130 ms 107.343 ms
15 ipv6gw00-cc1.rm-com.net (217.173.143.232) 141.839 ms 146.873 ms *
From what it seems like:
Toronto -> Albany -> Boston -> London -> Amsterdam -> France -> ? (it didn't even get to the destination!) |
|
js33
join:2007-03-10
Vancouver, WA
| I am quite certain that your traceroute in fact did get to its destination. 6to4 relay routers, per rfc, don't use 192.88.99.1 as source address for a reply. 192.88.99.1 is just an anycast address to reach the nearest relay. If you look at the PTR record that was retrieved for the last hop,
15 ipv6gw00-cc1.rm-com.net (217.173.143.232) 141.839 ms 146.873 ms *
You will see that it claims to be an IPv6 gateway of some sort. It's real (non-anycast) IPv4 address is 217.173.143.232. I can't say that it actually works, because I haven't tried it myself, but I would say two out of three of your test packets on the final hop did reach their destination. |
|
Deep Dish
join:2006-08-17
Canada | Ahh .. I should read up on that RFC then 
Thanks for the clarification! |
|
js33
join:2007-03-10
Vancouver, WA
| That's exactly the same router I get sent to, in fact. I used to have an IPv6 tunnel (freenet6) that went to Europe a few years ago, and it wasn't so bad, since Europe's rather ahead of N. America in IPv6 deployment anyways, and you might be going there anyways much of the time.
The real downside to a European tunnel is connectivity to Japan. (Lots of good IPv6 sites in Japan -- they're way ahead of the pack.) I don't think Europe and Asia have that good Internet connectivity with each other in general. Your v6 packets will come back from Europe over the Atlantic, cross the U.S., and head out from California to cross the Pacific before they go to Japan, if I remember correctly. You might get a whole second of latency by the time you add your tunnel in.
I don't know why Europe Asia traffic routes through the U.S. I think maybe the Internet started from the U.S. Gov't and fanned out from there, and maybe the NSA likes to slurp up what comes through. China will soon (and may already) be starting to route more of that traffic away from America, though.
Might be worth a shot, anyways, if just to map out the v6 world from France. |
|
jervin123
join:2005-04-14
Philadelphia, PA
| reply to justin236
I got this some what the same to yours but ended up in Relay, MD instead of seattle or where ever sea is.
Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
Tracing route to 192.88.99.1 over a maximum of 30 hops
1 3 ms 2 ms 2 ms 192.168.1.1
2 21 ms 22 ms 21 ms 66.173.189.249
3 88 ms 22 ms 22 ms 64.83.67.117
4 38 ms 25 ms 31 ms 64.83.67.30
5 25 ms 25 ms 24 ms 64.83.67.145
6 29 ms 28 ms 29 ms 66.16.64.61
7 32 ms 32 ms 33 ms sl-gw19-rly-4-0.sprintlink.net [144.232.150.137]
8 32 ms 32 ms 32 ms sl-bb20-rly-3-1.sprintlink.net [144.232.14.25]
9 34 ms 33 ms 33 ms 192.88.99.1 |
|
visitor
join:2001-07-26
Manchester, CT
| reply to justbits
This is a trace from on the Connecticut Education Network.
C:\tracert 192.88.99.1
Tracing route to 192.88.99.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 64.251.55.1
2 <1 ms <1 ms <1 ms 72.10.106.33
3 <1 ms <1 ms <1 ms ENFW043A.net.cen.ct.gov [72.10.106.42]
4 1 ms 1 ms <1 ms 72.10.116.18
5 2 ms 1 ms <1 ms 64.251.60.105
6 * * * Request timed out.
7 9 ms 8 ms 9 ms nox300gw1-PEER-NoX-INTERNET2-192-5-89-222.nox.org [192.5.8
9.222]
8 13 ms 13 ms 14 ms 64.57.28.3
9 23 ms 22 ms 22 ms beast-abilene-p3-0.3rox.net [192.88.115.125]
10 * * * Request timed out.
11 23 ms 23 ms 23 ms 192.88.99.1
Trace complete.
--
One minute... and Clarkson still sux! |
|
visitor
join:2001-07-26
Manchester, CT
| reply to justbits
Here is one from ISP Cox in Manchester CT.
traceroute 192.88.99.1
Type escape sequence to abort.
Tracing the route to 192.88.99.1
1 10.4.80.1 12 msec 12 msec 12 msec
2 mnchsysc01-gex0102000.ct.ri.cox.net (68.9.8.37) 24 msec 8 msec 8 msec
3 ip68-9-7-1.ri.ri.cox.net (68.9.7.1) 16 msec 56 msec 20 msec
4 provdsrj02-ge500.0.rd.ri.cox.net (68.9.14.105) 12 msec
provdsrj01-ge600.0.rd.ri.cox.net (68.9.14.101) 20 msec 44 msec
5 ashbbrj02-as0.0.r2.as.cox.net (68.1.1.232) 32 msec 28 msec 24 msec
6 89.167.141.66 120 msec 116 msec 116 msec
7 ffm-s1-rou-1022.DE.eurorings.net (134.222.231.213) 120 msec 116 msec 116 msec
8 mchn-s1-rou-1002.DE.eurorings.net (134.222.230.225) 128 msec 124 msec 124 msec
9 mchn-s1-rou-1072.DE.eurorings.net (134.222.112.86) 120 msec 124 msec 124 msec
10 kpn1-gw.teleport-iabg.de (134.222.112.75) 124 msec 136 msec 128 msec
11 access6-fa-0-1-92.teleport-iabg.de (83.170.0.56) 128 msec 148 msec *
--
One minute... and Clarkson still sux! |
|
justbits
More fiber than ATT can handle
Premium
join:2003-01-08
Chicago, IL
·AT&T Midwest
·AT&T Yahoo
| reply to justbits
AT+T DSL now routes through hotnic.net.
# traceroute 192.88.99.1
traceroute to 192.88.99.1 (192.88.99.1), 64 hops max, 40 byte packets
1 xxx (192.168.x.y) 2.103 ms 0.902 ms 1.314 ms
2 adsl-68-75-63-254.dsl.emhril.ameritech.net (68.75.63.254) 18.798 ms 10.809 ms 10.824 ms
3 dist1-vlan60.emhril.ameritech.net (68.22.72.130) 11.777 ms 10.715 ms 10.737 ms
4 bb1-g0-0.emhril.ameritech.net (151.164.43.82) 11.389 ms 12.456 ms 11.356 ms
5 151.164.94.41 (151.164.94.41) 12.443 ms 11.939 ms 12.219 ms
6 151.164.251.166 (151.164.251.166) 12.396 ms 13.760 ms 12.062 ms
7 so-0-3-0.was11.ip.tiscali.net (213.200.80.109) 33.554 ms 31.780 ms 31.759 ms
8 carpathia-gw158-1.ip.tiscali.net (213.200.66.66) 33.534 ms 33.757 ms 34.025 ms
9 iad0-b0-ge0.hotnic.net (66.117.34.140) 33.291 ms 33.413 ms 33.193 ms
10 192.88.99.1 (192.88.99.1) 32.826 ms 34.001 ms 32.327 ms
AT+T T1 (SBCIS Dedicated) routes 192.88.99.1 through hotnic.net.
traceroute 192.88.99.1
traceroute to 192.88.99.1 (192.88.99.1), 30 hops max, 40 byte packets
1 t1router (OUR.IP.AD.DR) 2.662 ms 1.515 ms 0.949 ms
2 THEM (TH.EM.BY.IP) 5.328 ms 5.24 ms 5.167 ms
3 bb1-g1-1-1.chcgil.ameritech.net (151.164.191.246) 5.538 ms 5.594 ms 5.303 ms
4 ex1-p0-0.eqchil.sbcglobal.net (151.164.42.147) 6.026 ms 6.054 ms 5.978 ms
5 asn3561-savvis.eqchil.sbcglobal.net (151.164.89.182) 6.78 ms 6.821 ms 6.676 ms
6 ber1-vlan-241.chicago.savvis.net (204.70.196.21) 6.811 ms 6.811 ms 7.103 ms
7 dcr2-so-4-3-0.chicago.savvis.net (208.175.10.237) 6.786 ms 6.882 ms 38.882 ms
8 dcr1-so-5-0-0.chicago.savvis.net (204.70.192.45) 8.317 ms bcs2-so-6-0-0.washington.savvis.net (204.70.192.29) 24.024 ms dcr1-so-5-0-0.chicago.savvis.net (204.70.192.45) 10.945 ms
9 cpr2-pos-9-0.virginiaequinix.savvis.net (204.70.193.154) 22.609 ms cpr1-pos-15-0.virginiaequinix.savvis.net (206.24.238.218) 22.781 ms bcs1-so-1-3-0.washington.savvis.net (204.70.192.21) 24.125 ms
10 ber1-tenge-3-1.virginiaequinix.savvis.net (204.70.193.102) 233.283 ms cpr2-pos-15-3.virginiaequinix.savvis.net (206.24.227.106) 22.679 ms cpr2-pos-6-2.virginiaequinix.savvis.net (206.24.238.98) 22.74 ms
11 208.173.10.250 (208.173.10.250) 24.472 ms ber1-tenge-3-1.virginiaequinix.savvis.net (204.70.193.102) 23.954 ms 208.173.10.250 (208.173.10.250) 24.291 ms
12 iad0-b0-ge0.hotnic.net (66.117.34.140) 24.79 ms 208.173.10.250 (208.173.10.250) 24.185 ms iad0-b0-ge0.hotnic.net (66.117.34.140) 24.677 ms
13 iad0-b0-ge0.hotnic.net (66.117.34.140) 24.539 ms 24.559 ms 192.88.99.1 (192.88.99.1) 25.302 ms
I'm not sure when this changed. Guess I'll have to start pinging it. |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| reply to justbits
at&t Yahoo! HSI (formerly SBC, and PacBell):
Tracing route to 192.88.99.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms chihiro.aosake.net [192.168.102.1]
2 2 ms 1 ms 1 ms suzuka.aosake.net [192.168.0.1]
3 11 ms 10 ms 10 ms adsl-68-125-51-254.dsl.pltn13.pacbell.net [68.125.51.254]
4 10 ms 11 ms 10 ms dist1-vlan60.pltn13.pbi.net [64.164.97.130]
5 10 ms 10 ms 10 ms bb1-g15-0.pltnca.sbcglobal.net [151.164.93.231]
6 12 ms 12 ms 11 ms ex2-p12-0.eqsjca.sbcglobal.net [151.164.94.47]
7 12 ms 12 ms 18 ms so-0-1-2.sjc11.ip.tiscali.net [213.200.66.245]
8 85 ms 85 ms 85 ms so-1-0-0.was11.ip.tiscali.net [213.200.80.94]
9 85 ms 84 ms 84 ms carpathia-gw158-1.ip.tiscali.net [213.200.66.66]
10 84 ms 84 ms 85 ms iad0-b0-ge0.hotnic.net [66.117.34.140]
11 86 ms 85 ms 84 ms 192.88.99.1
Trace complete.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
kshymkiw
join:2004-12-21
Columbus, OH
| TWC in Columbus, Ohio
C:\Documents and Settings\kevin s>tracert 192.88.99.1
Tracing route to 192.88.99.1 over a maximum of 30 hops
1 1 ms 1 ms 1 ms rrcs-24-123-158-75.central.biz.rr.com [24.123.15
8.75]
2 4 ms 5 ms 2 ms vln972.clmboh1-swt103.columbus.rr.com [24.106.16
4.201]
3 1 ms 1 ms 1 ms gig6-0-802.clmboh1-rtr4.columbus.rr.com [24.106.
165.30]
4 7 ms 7 ms 7 ms son0-1-2.ncntoh1-rtr0.neo.rr.com [65.25.128.221]
5 10 ms 11 ms 18 ms gig7-3-0.mtgmoh1-rtr0.columbus.rr.com [24.95.81.
209]
6 11 ms 12 ms 11 ms te-3-1.car1.Cincinnati1.Level3.net [4.78.216.9]
7 29 ms 19 ms 17 ms ae-5-5.ebr2.Chicago1.Level3.net [4.69.132.206]
8 37 ms 36 ms 35 ms ae-2.ebr2.Washington1.Level3.net [4.69.132.70]
9 57 ms 202 ms 211 ms ae-23-52.car3.Washington1.Level3.net [4.68.121.4
8]
10 53 ms 32 ms 47 ms 4.79.18.82
11 34 ms 32 ms 34 ms iad0-b0-ge0.hotnic.net [66.117.34.140]
12 32 ms 32 ms 33 ms 192.88.99.1
Trace complete. |
|
Matt
Gone playing Dragon Age Origins
Premium
join:2003-07-20
Jamestown, NC
·North State Commun..
1 edit | reply to justbits
I win! (So far)
My home North State BPON fiber connection.
Tracing route to 192.88.99.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms neurotransmit.neural.local [192.168.1.1]
2 13 ms 9 ms 12 ms 216-237-229-130 [216.237.229.130]
3 11 ms 12 ms 9 ms 216-237-229-130 [216.237.229.130]
4 11 ms 9 ms 12 ms juniper-2.nstel.com [216.237.229.2]
5 11 ms 12 ms 9 ms GigabitEthernet2-1.GW2.GSO1.ALTER.NET [157.130.38.133]
6 12 ms 12 ms 12 ms 0.so-4-0-1.XL2.Gso1.ALTER.NET [152.63.36.142]
7 17 ms 17 ms 19 ms 0.so-4-2-0.XT2.DCA5.ALTER.NET [152.63.40.42]
8 19 ms 19 ms 19 ms 0.so-7-0-0.BR1.DCA5.ALTER.NET [152.63.43.177]
9 16 ms 19 ms 19 ms 204.255.168.14
10 22 ms 19 ms 19 ms sl-bb24-rly-8-0.sprintlink.net [144.232.20.154]
11 21 ms 19 ms 19 ms sl-bb20-rly-10-0.sprintlink.net [144.232.14.121]
12 18 ms 22 ms 19 ms 192.88.99.1
Trace complete.
Our datacenter rack (Time Warner) connection:
Tracing route to 192.88.99.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms rrcs-24-199-166-49.midsouth.biz.rr.com [24.199.1
66.49]
2 <1 ms <1 ms <1 ms rrcs-24-199-166-249.midsouth.biz.rr.com [24.199.
166.249]
3 <1 ms <1 ms <1 ms srp2-0.gnboncsg-rtr4.triad.rr.com [24.28.226.212
]
4 3 ms 3 ms 3 ms son0-0-2.chrlncsa-rtr6.carolina.rr.com [24.93.64
.41]
5 3 ms 3 ms 3 ms pop1-cha-p4-0.atdn.net [66.185.132.45]
6 3 ms 3 ms 3 ms bb1-cha-p3-0.atdn.net [66.185.138.64]
7 8 ms 8 ms 8 ms bb1-atm-p6-0.atdn.net [66.185.152.182]
8 8 ms 8 ms 8 ms pop1-atm-p1-0.atdn.net [66.185.147.193]
9 8 ms 8 ms 8 ms sl-bb23-atl-10-2.sprintlink.net [144.232.8.209]
10 8 ms 8 ms 8 ms sl-bb20-atl-9-0.sprintlink.net [144.232.12.13]
11 24 ms 24 ms 24 ms sl-bb25-rly-3-0.sprintlink.net [144.232.20.175]
12 25 ms 24 ms 24 ms sl-bb22-rly-12-0.sprintlink.net [144.232.14.165]
13 25 ms 25 ms 25 ms 192.88.99.1
Trace complete. |
|
merriam
Premium
join:2004-05-04
Gainesville, FL
| Here is "The New AT&T"
traceroute to 192.88.99.1 (192.88.99.1), 30 hops max, 40 byte packets
1 68.208.230.3 (68.208.230.3) 7.275 ms 7.460 ms 7.337 ms
2 65.14.213.209 (65.14.213.209) 9.888 ms 8.956 ms 12.060 ms
3 axr00mco-so-1-0-0.bellsouth.net (65.83.239.40) 11.532 ms 13.762 ms 17.109 ms
4 ber01gnv-pos-4-0-0.bellsouth.net (65.83.239.41) 11.535 ms 13.995 ms 10.920 ms
5 axr00mco-so-1-0-0.bellsouth.net (65.83.239.40) 15.285 ms 18.202 ms 16.505 ms
6 ber01gnv-pos-4-0-0.bellsouth.net (65.83.239.41) 14.715 ms 17.067 ms 16.851 ms
7 axr00mco-so-1-0-0.bellsouth.net (65.83.239.40) 18.316 ms 17.552 ms 18.055 ms
8 ber01gnv-pos-4-0-0.bellsouth.net (65.83.239.41) 17.403 ms 17.152 ms 20.445 ms
9 axr00mco-so-1-0-0.bellsouth.net (65.83.239.40) 21.516 ms 21.302 ms 21.016 ms
10 ber01gnv-pos-4-0-0.bellsouth.net (65.83.239.41) 21.453 ms 21.515 ms 21.382 ms
11 axr00mco-so-1-0-0.bellsouth.net (65.83.239.40) 23.848 ms 26.592 ms 25.013 ms
12 ber01gnv-pos-4-0-0.bellsouth.net (65.83.239.41) 24.808 ms 26.188 ms 27.245 ms
13 axr00mco-so-1-0-0.bellsouth.net (65.83.239.40) 30.150 ms 30.696 ms 30.694 ms
14 ber01gnv-pos-4-0-0.bellsouth.net (65.83.239.41) 31.676 ms 29.391 ms 29.001 ms
15 axr00mco-so-1-0-0.bellsouth.net (65.83.239.40) 31.959 ms 36.812 ms 36.331 ms
16 ber01gnv-pos-4-0-0.bellsouth.net (65.83.239.41) 37.037 ms 36.888 ms 37.743 ms
17 axr00mco-so-1-0-0.bellsouth.net (65.83.239.40) 39.290 ms 39.102 ms 40.269 ms
18 ber01gnv-pos-4-0-0.bellsouth.net (65.83.239.41) 41.768 ms 41.982 ms 42.536 ms
19 axr00mco-so-1-0-0.bellsouth.net (65.83.239.40) 46.740 ms 45.237 ms 45.710 ms
20 ber01gnv-pos-4-0-0.bellsouth.net (65.83.239.41) 41.498 ms 42.260 ms 43.312 ms
21 axr00mco-so-1-0-0.bellsouth.net (65.83.239.40) 47.390 ms 48.648 ms 48.207 ms
22 ber01gnv-pos-4-0-0.bellsouth.net (65.83.239.41) 48.472 ms 46.478 ms 46.929 ms
23 axr00mco-so-1-0-0.bellsouth.net (65.83.239.40) 49.672 ms 51.523 ms 51.906 ms
24 ber01gnv-pos-4-0-0.bellsouth.net (65.83.239.41) 49.443 ms 49.224 ms 48.083 ms
25 * * *
26 ber01gnv-pos-4-0-0.bellsouth.net (65.83.239.41) 50.823 ms 47.443 ms 48.896 ms
27 * * *
28 ber01gnv-pos-4-0-0.bellsouth.net (65.83.239.41) 50.129 ms 48.851 ms 51.331 ms
29 axr00mco-so-1-0-0.bellsouth.net (65.83.239.40) 55.023 ms 55.301 ms 54.277 ms
30 ber01gnv-pos-4-0-0.bellsouth.net (65.83.239.41) 56.343 ms 54.314 ms 54.412 ms |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
2 edits | It looks like you aren't fully integrated into AT&T just yet...
See my "new" AT&T trace route a few posts up (and 'justbits', just before mine).
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
rovernet
Premium
join:2004-02-11
Richardson, TX
 ·AT&T U-Verse
| reply to justbits
Here's from a Road Runner, soon to be renamed Comcast:
1 2 ms 2 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 * 8 ms 7 ms gig1-1-3.hstntxtid-rtr1.houston.rr.com [24.28.102.9]
4 8 ms 10 ms 17 ms gig12-0-0.hstntxtid-rtr3.texas.rr.com [24.93.34.94]
5 20 ms 25 ms 24 ms gig1-3-0.dllatxl3-rtr1.texas.rr.com [72.179.205.5]
6 21 ms 23 ms 19 ms pop2-dls-P4-3.atdn.net [66.185.133.105]
7 20 ms 19 ms 21 ms bb1-dls-P1-0.atdn.net [66.185.133.96]
8 41 ms 51 ms 40 ms bb2-chi-P4-0.atdn.net [66.185.152.13]
9 41 ms * 41 ms pop1-chi-P1-0.atdn.net [66.185.141.87]
10 54 ms 54 ms 57 ms Sprint.atdn.net [66.185.150.218]
11 * * 54 ms sl-crs2-chi-0-0-0-3.sprintlink.net [144.232.26.9]
12 53 ms 57 ms 54 ms sl-bb25-chi-8-0.sprintlink.net [144.232.26.113]
13 39 ms 39 ms 40 ms sl-bb20-kc-2-0.sprintlink.net [144.232.20.108]
14 39 ms 39 ms 44 ms sl-bb25-fw-13-0.sprintlink.net [144.232.20.4]
15 40 ms 43 ms 41 ms 192.88.99.1
Trace complete. |
|
