Anonymous_
Anonymous
Premium
join:2004-06-21
127.0.0.1
clubs:
2 edits | IP data Loops around the US
any reason why ip data has to take an Tour the US before coming back to the west cost?
it adds 50 extra ms
just to AZ the ping times are 99ms
to NY 121ms
up from 35ms and up from 100ms to NY |
|
hobgoblin
Sortof Agoblin
Premium
join:2001-11-25
Orchard Park, NY
clubs: | Terrible......a couple of traces might be good to see
Hob |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
 ·Pacific Bell - SBC
| reply to Anonymous_
Show us. I know that Comcast users in northern Oregon (near Corvallis) are routed to Seattle to get out to other parts of the U.S. And ATTIS (network behind at&t Yahoo! HSI) users in southern California are routed to San José, California, to get out to other parts of the U.S. That last can lead to routes running from Los Angeles, to San José, then back to Los Angeles, before heading east.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
dwilson805
Premium
join:2005-07-22
Hanceville, AL
 ·RoadRunner Cable
| reply to hobgoblin
said by hobgoblin  :Terrible......a couple of traces might be good to see Hob I am not the OP, but I have also seen latency increasing over the past few weeks. The following trace is from my business-class connection in Alabama to Los Angeles:
Tracing route to www.dslextreme.com [66.51.205.15]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.4.3
2 10 ms 8 ms * mta-65-28-144-1.natsoe.res.rr.com [65.28.144.1]
3 10 ms 9 ms * gig3-1.clmnal-rtr1.natsoe.rr.com [65.28.203.45]
4 21 ms 23 ms * so-2-0-1.atlaga-rtr2.peakview.rr.com [65.28.203.69]
5 24 ms 21 ms * ge-2-3-0.cr1.atl20.tbone.rr.com [66.109.6.174]
6 37 ms 37 ms * ae-4-0.cr0.dca10.tbone.rr.com [66.109.6.33]
7 38 ms 39 ms * ae-1-0.pr0.dca20.tbone.rr.com [66.109.6.183]
8 40 ms 41 ms * 64.124.196.81.available.above.net [64.124.196.81]
9 42 ms 41 ms * so-5-0-0.mpr2.iad1.us.above.net [64.125.27.209]
10 40 ms 39 ms * so-3-0-0.mpr1.iad2.us.above.net [64.125.29.134]
11 39 ms 50 ms * so-3-0-0.mpr1.iad10.us.above.net [64.125.30.117]
12 41 ms 37 ms * above-oc48.iad.att.net [64.125.13.14]
13 117 ms 93 ms 94 ms tbr2.wswdc.ip.att.net [12.122.80.18]
14 93 ms 93 ms 92 ms cr2.wswdc.ip.att.net [12.122.16.69]
15 93 ms 93 ms 91 ms cr1.attga.ip.att.net [12.122.1.173]
16 94 ms 92 ms 99 ms cr2.dlstx.ip.att.net [12.122.28.174]
17 93 ms 95 ms 94 ms cr2.la2ca.ip.att.net [12.122.28.178]
18 96 ms 95 ms 94 ms tbr2.la2ca.ip.att.net [12.122.19.214]
19 93 ms 93 ms 91 ms 12.122.104.85
20 94 ms 93 ms 92 ms 12.116.103.58
21 95 ms 93 ms 93 ms lax1.ns50.eth3.dslextreme.com [66.51.199.20]
22 96 ms 99 ms 94 ms www.dslextreme.com [66.51.205.15]
I ignored the third ping that was dropped, as it is my understanding that Roadrunner rate-limits pings.
The big jump appears to be once the signal crosses onto AT&T's backbone, but it certainly seems to be a circuitous route? |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| I think that IAD is the code for Dulles International Airport, in Washington, D.C. Road Runner is taking you east to Atlanta, then north to Washington, D.C. to connect you to Abovenet Communications. Abovenet is handing you off to AT&T Worldnet Services there, and ATTW runs you back to Atlanta, Georgia, then west to Dallas, Texas, and Los Angeles, California.
A lot depends upon the peering arrangements with the transit providers. I really don't have a good handle on those (the peering arrangements); but, if RR has to go through Abovenet, and DSL Extreme gets transit from ATTW, you are pretty much at the mercy of where those companies agree to interconnect.
I don't think that there is a regional interconnect hub anywhere in Alabama. Internet routing is kind of like flying around the country. Sometimes you have to fly west from Reno, Nevada, to Sacramento, California, before you can go east to Chicago, Illinois.
Unless you move to one of the locations of interconnect hubs. (Nice to live in San José, California!)
Hop 8 is Road Runner in San José. But the Road Runner 'tbone' regional transit network heads east to Atlanta, Georgia, before splitting off Alabama traffic and shipping it back west.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
dwilson805
Premium
join:2005-07-22
Hanceville, AL
·RoadRunner Cable
| said by NormanS :I don't think that there is a regional interconnect hub anywhere in Alabama. Internet routing is kind of like flying around the country. Sometimes you have to fly west from Reno, Nevada, to Sacramento, California, before you can go east to Chicago, Illinois. It appears from my traceroutes that RR sends everything from AL to Atlanta and then to DC. If I tracert to an address 5 miles from here that is on bellsouth, it still goes to DC before moving over to the bellsouth network and coming back to Alabama. At least in that case, however, there isn't a bad hop in the mix, as there is in the AT&T trace above, so latency stays around 50ms. |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
1 edit | Bad hop? High latency? 90ms from Alabama to California would be a tad high if you went straight from Alabama to California; but you head east, almost to the Atlantic before heading west, almost to the Pacific. 90 ms for Atlantic shore to Pacific shore is about right.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
