| reply to houkouonchi
Re: U-Verse is FTTP? FTTP uses Ethernet from the ONT to the RG at 100Mbps. No interleaving on fiber and no VDSL on AT&T FTTP equipment that I have installed. |
|
| reply to ztmike
Damn, I might have actually been willing to drop my DSL for u-verse if I was in an FTTP area. Can anyone on FTTP show me a traceroute to a close server? |
|
|
|
| tracert mail.yahoo.com
Tracing route to login.lga1.b.yahoo.com [209.191.92.114]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.254
2 2 ms 2 ms 2 ms 99-11-252-2.lightspeed.austtx.sbcglobal.net [99.11.252.2]
3 * * * Request timed out.
4 * * * Request timed out.
5 5 ms 2 ms 2 ms 75.8.128.14
6 3 ms 2 ms 1 ms bb1-g2-0.austtx.sbcglobal.net [151.164.92.90]
7 9 ms 9 ms 8 ms ex2-p14-0.eqdltx.sbcglobal.net [151.164.41.155]
8 15 ms 8 ms 9 ms asn10310-10-yahoo.eqdltx.sbcglobal.net [151.164.250.10]
9 10 ms 10 ms 9 ms ae2-p101.msr1.mud.yahoo.com [216.115.104.107]
10 10 ms 10 ms 10 ms te-9-1.bas-c1.mud.yahoo.com [68.142.193.9]
11 9 ms 10 ms 9 ms l2.login.vip.mud.yahoo.com [209.191.92.114]
Trace complete. |
|
 ILpt4UPremium
join:2006-11-12
Lisle, IL
kudos:4 | 10 ms from Austin to San Fran ain't too shabby...
I'm jealous =) |
|
Reviews:
 ·Verizon FiOS
 ·Charter
·AT&T U-Verse
 ·DSL EXTREME
| said by ILpt4U:10 ms from Austin to San Fran ain't too shabby... I'm jealous =) It is nice, but that IP is not in san fransisco, its in texas. The 2ms latency to the backbone in Austin is pretty nice though.
--
Chugging along on 2x 6016/768k DSL Extreme DSL lines and one 6016/768 ATT DSL DIrect line as well as one 16mb/2mb Charter cable line for a combined total of just over 32 meg download and 3 meg up (after overhead). yay! |
|
ILpt4UPremium
join:2006-11-12
Lisle, IL
kudos:4 | Really?
I used a few different IP locator websites, and they all said San Fran
Of course IP locators are not always perfect |
|
Reviews:
·Verizon FiOS
·Charter
·AT&T U-Verse
·DSL EXTREME
| Yup, alot of them are inaccurate. Also 10ms from texas -> califrnia = impossible. You can see it spikes to 8-9ms just by the time it hits eqdltx which I would say is also in texas. Here is a traceroute to that IP from socal which shows much worse latency to that IP than northern california:
# traceroute -i eth3 209.191.92.114 -I
traceroute to l2.login.vip.mud.yahoo.com (209.191.92.114), 30 hops max, 46 byte packets
1 ip-66-33-193-2 (66.33.193.2) 2.320 ms 7.958 ms 8.475 ms
2 nav-core02 (66.33.201.65) 8.729 ms 3.740 ms 1.738 ms
3 ge-0-1-0.405.ar1.LAX3.gblx.net (67.17.162.161) 1.997 ms 1.246 ms 0.979 ms
4 te9-4-10GE.ar2.LAX1.gblx.net (67.17.75.97) 0.974 ms 5.172 ms 3.741 ms
5 yahoo-1.ar2.LAX2.gblx.net (64.208.110.122) 2.229 ms 1.019 ms 2.255 ms
6 so-2-0-0.pat1.dax.yahoo.com (216.115.96.50) 62.182 ms 58.960 ms 66.440 ms
7 ae2-p110.msr2.mud.yahoo.com (216.115.104.109) 65.935 ms 60.581 ms ae2-p100.msr1.mud.yahoo.com (216.115.104.105) 62.438 ms
8 te-9-1.bas-c2.mud.yahoo.com (68.142.193.11) 61.031 ms 68.287 ms te-8-1.bas-c2.mud.yahoo.com (68.142.193.7) 67.940 ms
9 l2.login.vip.mud.yahoo.com (209.191.92.114) 65.270 ms 62.384 ms 65.944 ms
# traceroute -i eth3 sfo.speakeasy.net -I
traceroute to dns.sfo1.speakeasy.net (64.81.79.2), 30 hops max, 46 byte packets
1 ip-66-33-193-2 (66.33.193.2) 0.953 ms 0.436 ms 0.494 ms
2 nav-core02 (66.33.201.65) 26.963 ms 191.837 ms 1.967 ms
3 border21.ge4-3.newdream-8.lax.pnap.net (216.52.220.145) 1.733 ms 0.467 ms 0.740 ms
4 core2.po2-20g-bbnet2.lax.pnap.net (216.52.255.66) 1.241 ms 2.122 ms 3.244 ms
5 GigabitEthernet2-0-0.GW3.LAX15.ALTER.NET (157.130.236.109) 9.721 ms 0.474 ms 0.487 ms
6 0.so-4-0-0.XL1.LAX15.ALTER.NET (152.63.112.106) 12.231 ms 0.489 ms 1.213 ms
7 0.so-5-2-0.XT1.LAX7.ALTER.NET (152.63.1.225) 1.488 ms 1.097 ms 1.495 ms
8 p64-5-0-1.r20.lsanca03.us.bb.gin.ntt.net (129.250.8.69) 0.973 ms 2.597 ms 3.976 ms
9 as-0.r21.snjsca04.us.bb.gin.ntt.net (129.250.4.96) 10.230 ms 12.365 ms 9.965 ms
MPLS Label=648487 CoS=0 TTL=255 S=0
MPLS Label=354561 CoS=0 TTL=1 S=1
10 ae-0.r20.plalca01.us.bb.gin.ntt.net (129.250.4.118) 14.465 ms 11.779 ms 12.985 ms
MPLS Label=354561 CoS=0 TTL=255 S=1
11 xe-3-4.r04.plalca01.us.bb.gin.ntt.net (129.250.4.242) 166.656 ms 203.512 ms 203.056 ms
12 140.174.28.114 (140.174.28.114) 11.730 ms 11.982 ms 12.229 ms
13 dns.sfo1.speakeasy.net (64.81.79.2) 14.974 ms 11.414 ms 11.251 ms
Latency from socal -> texas is usually more around 30-40 ms + gateway latency:
# traceroute -i eth3 dfw.speakeasy.net -I
traceroute to dns.dfw1.speakeasy.net (64.81.127.2), 30 hops max, 46 byte packets
1 ip-66-33-193-2 (66.33.193.2) 2.670 ms 0.790 ms 0.473 ms
2 nav-core02 (66.33.201.65) 0.479 ms 0.575 ms 0.497 ms
3 border21.ge4-3.newdream-8.lax.pnap.net (216.52.220.145) 1.469 ms 3.373 ms 2.734 ms
4 core2.po2-20g-bbnet2.lax.pnap.net (216.52.255.66) 3.230 ms 0.851 ms 0.730 ms
5 GigabitEthernet2-0-0.GW3.LAX15.ALTER.NET (157.130.236.109) 0.494 ms 3.057 ms 3.480 ms
6 0.so-4-0-0.XL2.LAX15.ALTER.NET (152.63.112.110) 2.989 ms 0.578 ms 0.662 ms
7 0.so-7-3-0.XT2.LAX7.ALTER.NET (152.63.112.62) 0.746 ms 3.398 ms 2.226 ms
8 p64-5-0-1.r20.lsanca03.us.bb.gin.ntt.net (129.250.8.69) 1.722 ms 0.697 ms 0.740 ms
9 as-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.2.169) 35.470 ms 37.027 ms 38.452 ms
MPLS Label=300352 CoS=0 TTL=255 S=1
10 po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74) 35.714 ms 33.873 ms 34.200 ms
11 ge-3-3.r01.dllstx09.us.bb.gin.ntt.net (157.238.224.78) 38.213 ms 39.777 ms 40.389 ms
12 dns.dfw1.speakeasy.net (64.81.127.2) 37.960 ms 36.489 ms 43.198 ms
--
Chugging along on 2x 6016/768k DSL Extreme DSL lines and one 6016/768 ATT DSL DIrect line as well as one 16mb/2mb Charter cable line for a combined total of just over 32 meg download and 3 meg up (after overhead). yay! |
|
Reviews:
 ·Clear Wireless
| reply to ILpt4U
said by houkouonchi:Almost zero. Seriously, the normal ping in my area for a VDSL customer to Chicago speedtest.net servers is ~25 ms. For a FTTP customer, it is ~4 ms. Much quicker pings. I'm one of those in the Chicago area that has the 20ms ping on the 1st hop. It is slightly annoying but it is tolerable. FTTP would be nice but i doubt it will ever happen in my area since it is nothing but copper and old homes. |
|
