NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
 ·Pacific Bell - SBC
| reply to flycuban
Re: Just the beginging
said by flycuban  :I guess each "Region" has there own peering sites, because here in Florida most if not all the traffic goes thru at&t.. Hardly none of the traffic goes on the Comcast national backbone... Indeed. However, isn't Florida one of the regions Comcast picked up from Road Runner? Perhaps Comcast hasn't, yet, built out their backbone in the Southeastern U.S.?
One Global Crossing (Tier 1 backbone provider) hop between ATTIS (my provider's backbone) and Comcast's 'ibone' network.
One Level 3 (Tier 1 backbone provider) hop between ATTIS (my provider's backbone) and Comcast's 'ibone' network.
All connections to West Coast destinations are made right here in San José, California.
Seven Level 3 (Tier 1 backbone) hops between ATTIS in San José, California and the Comcast 'ibone' network in Chicago, Illinois.
I would guess that Comcast just has to put in their 'ibone' in the Southeast, based on trace routes to '.hsd1.ga.comcast.net' and '.hsd1.fl.comcast.net' from the West Coast.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
1 edit | reply to Doug135
Mark the difference between AT&T Internet Services (ATTIS), which provides your network connections to other transit services, and AT&T Worldnet Services (ATTW), which is the Tier 1 backbone transit provider offering services comparable to Level 3, Qwest, and Verizon (Business); all of which are also Tier 1 networks.
ATTIS will only connect with ATTW when routing tables call for it.
You, as an at&t Yahoo! HSI customer, will be on the ATTIS network until it connects with a destination transit provider, as announced in BGP by the destination.
P.S. I forgot to mention that ATTIS will connect directly to Google, Microsoft, and Yahoo! networks, without going through any other transit. At least for all trace routes I have ever run to them.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
Doug135
join:2008-01-12
Laredo, TX
clubs:
·AT&T Southwest
| reply to dadkins
i've got AT&T and i trace routed 209.191.93.52 and i got:
1 1 ms 1 ms 1 ms 192.168.1.1
2 264 ms 274 ms 202 ms ppp-70-244-249-254.dsl.snantx.swbell.net [70.244.249.254]
3 151 ms 72 ms 127 ms dist2-vlan60.snantx.sbcglobal.net [151.164.17.163]
4 407 ms 155 ms 98 ms bb1-g9-3-0.snantx.sbcglobal.net [151.164.17.246]
5 385 ms 564 ms * 151.164.95.188
6 427 ms 496 ms 397 ms asn10310-11-yahoo.eqdltx.sbcglobal.net [151.164.250.202]
7 499 ms 334 ms 297 ms ge-0-1-0-p110.msr2.mud.yahoo.com [216.115.104.101]
8 147 ms 435 ms 252 ms te-9-1.bas-c1.mud.yahoo.com [68.142.193.9]
9 301 ms 349 ms 432 ms f1.www.vip.mud.yahoo.com [209.191.93.52]
Trace complete.
i tried 68.86.220.145 and it switches from sbc servers to level3 servers and then to the comcast servers. i take it as at&t peers with others as well. |
|
dadkins
Can you do Blu?
Premium,MVM
join:2003-09-26
Hercules, CA
 ·Comcast
| reply to flycuban
I'm not doubting that.
Nearly all of Comcast traffic here used to go through AT&T a couple years ago.
Not anymore!
For some routes, sure! AT&T, Gblx, Level3...
For *most* things, here in my part of the State, it stays on Comcast across the country.
--
Think outside the Fox... Opera |
|
flycuban
join:2005-04-25
Homestead, FL | reply to dadkins
I guess each "Region" has there own peering sites, because here in Florida most if not all the traffic goes thru at&t.. Hardly none of the traffic goes on the Comcast national backbone... |
|
en102
Canadian, eh?
join:2001-01-26
Valencia, CA | reply to dadkins
Similarly, DSL-Extreme uses multiple, including Level3
--
Canada = Hollywood North |
|
dadkins
Can you do Blu?
Premium,MVM
join:2003-09-26
Hercules, CA
·Comcast
1 edit | reply to flycuban
You stated that "Comcast uses at&t as there main backbone internet provider..."
I showed you that in most cases, they do not - at least from here in California.
For that Yahoo address you used: 209.191.93.52...
No AT&T here - I see Level3.
Comcast will peer with whomever is closest if needed.
Not just AT&T.
For most national backbone tasks, Comcast will use their own - for many of us!
YMMV
--
Think outside the Fox... Opera |
|
flycuban
join:2005-04-25
Homestead, FL
| reply to dadkins
NOT FROM MIAMI - Almost all of our traffic is on at&t bro.
Tracing route to msnbc.com [207.46.245.61]
over a maximum of 30 hops:
1 4 ms 16 ms 7 ms 192.168.1.1
2 * * * Request timed out.
3 103 ms 7 ms * ge-1-2-ur01.perrine.fl.pompano.comcast.net [68.8
5.229.57]
4 11 ms 12 ms 9 ms te-9-2-ar01.miamimetro.fl.pompano.comcast.net [6
8.86.165.37]
5 10 ms * 10 ms po-1-ar02.pompanobeach.fl.pompano.comcast.net [6
8.86.164.13]
6 19 ms 24 ms 20 ms 12.116.114.13
7 100 ms 100 ms 100 ms tbr1.ormfl.ip.att.net [12.122.106.6]
8 107 ms 108 ms 107 ms cr1.ormfl.ip.att.net [12.122.21.1]
9 101 ms 99 ms 105 ms cr2.attga.ip.att.net [12.122.31.29]
10 101 ms 101 ms 100 ms tbr1.attga.ip.att.net [12.122.17.14]
11 100 ms 100 ms 100 ms tbr2.dtrmi.ip.att.net [12.122.10.197]
12 100 ms 100 ms 100 ms tbr2.cgcil.ip.att.net [12.122.10.134]
13 99 ms 98 ms 101 ms cr1.cgcil.ip.att.net [12.122.17.201]
14 106 ms 100 ms 100 ms cr1.st6wa.ip.att.net [12.122.31.162]
15 104 ms 99 ms 100 ms tbr1.st6wa.ip.att.net [12.122.23.130]
16 100 ms 100 ms 100 ms 12.127.6.33
17 91 ms 92 ms 91 ms 12.124.173.42
18 92 ms 97 ms 91 ms ge-5-3-0-56.tuk-64cb-1a.ntwk.msn.net [207.46.44.
1]
19 102 ms 91 ms 91 ms ten2-1.tuk-76c-1b.ntwk.msn.net [207.46.36.201]
-------------------------------------------------
Tracing route to www.yahoo-ht3.akadns.net [209.191.93.52]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 9 ms * ge-1-2-ur01.perrine.fl.pompano.comcast.net [68.8
5.229.57]
4 9 ms 10 ms * te-9-2-ar01.miamimetro.fl.pompano.comcast.net [6
8.86.165.37]
5 11 ms * * po-1-ar02.pompanobeach.fl.pompano.comcast.net [6
8.86.164.13]
6 18 ms 18 ms 19 ms 12.116.114.13
7 52 ms 51 ms 50 ms tbr1.ormfl.ip.att.net [12.122.106.6]
8 50 ms 51 ms 51 ms cr1.ormfl.ip.att.net [12.122.21.17]
9 52 ms 51 ms 50 ms cr1.hs1tx.ip.att.net [12.122.31.241]
10 50 ms 50 ms 50 ms cr2.dlstx.ip.att.net [12.122.5.233]
11 52 ms 50 ms 51 ms tbr2.dlstx.ip.att.net [12.122.18.206]
12 51 ms 49 ms 50 ms gar8.dlstx.ip.att.net [12.122.100.81]
13 53 ms 52 ms 52 ms 12.86.20.18
14 107 ms 54 ms 54 ms ge-0-1-0-p110.msr2.mud.yahoo.com [216.115.104.10
1]
15 54 ms 52 ms 51 ms te-8-1.bas-c2.mud.yahoo.com [68.142.193.7]
16 57 ms 53 ms 52 ms f1.www.vip.mud.yahoo.com [209.191.93.52]
-------------------------------------------------
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator>tracert www.cnn.com
Tracing route to www.cnn.com [64.236.16.20]
over a maximum of 30 hops:
1 20 ms 2 ms 5 ms 192.168.1.1
2 * * * Request timed out.
3 60 ms 199 ms 199 ms ge-1-2-ur01.perrine.fl.pompano.comcast.net [68.8
5.229.57]
4 9 ms 9 ms * te-9-2-ar01.miamimetro.fl.pompano.comcast.net [6
8.86.165.37]
5 10 ms * 11 ms po-1-ar02.pompanobeach.fl.pompano.comcast.net [6
8.86.164.13]
6 18 ms 18 ms 19 ms 12.116.114.13
7 28 ms 27 ms 28 ms tbr1.ormfl.ip.att.net [12.122.106.6]
8 28 ms 28 ms 26 ms cr1.ormfl.ip.att.net [12.122.21.9]
9 27 ms 28 ms 28 ms cr2.attga.ip.att.net [12.122.31.29]
10 28 ms 28 ms 28 ms tbr1.attga.ip.att.net [12.122.17.6]
11 27 ms 26 ms 26 ms ggr3.attga.ip.att.net [12.122.96.9]
12 27 ms 26 ms 25 ms br1-a340s7.wswdc.ip.att.net [192.205.34.162]
13 26 ms 26 ms 26 ms bb1-atm-P4-0.atdn.net [66.185.147.208] |
|
