dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1626
share rss forum feed


warlock56
Premium
join:2002-07-31
Arlington, TX

What is your routing to dslreports.com?

Click for full size
Lately I've been playing a some fps games on occasion. I'd been off of them for a couple of years now actually; I don't know what made me decide to try them again.

So anyway one thing I've noticed in different fps games is my ping time is typically at least in the 100ms range. When was on at&t my ping time was usually better, probably around 60ms range. There are still some servers that have better ping response than others, but by and large most of them are on the high side, which leads me to believe the routing TWC is using may be causing the lag.

So I'm posting a traceroute from my computer to dslreports.com that was taken just a few minutes ago. I'm curious to know, especially from other users who live in the same area, what your routing looks like.
--
The moment the idea is admitted into society, that property is not as sacred as the laws of God, and that there is not a force of law and public justice to protect it, anarchy and tyranny commence. -John Adams, 1787


NormanS
I gave her time to steal my mind away
Premium,MVM
join:2001-02-14
San Jose, CA
kudos:12
Reviews:
·SONIC.NET
·Pacific Bell - SBC
Tracing route to www.dslreports.com [209.123.109.175]
over a maximum of 30 hops:
 
  1     2 ms     2 ms    10 ms  Chihiro [192.168.102.1]
  2    29 ms    28 ms    38 ms  173-228-7-1.dsl.static.sonic.net [173.228.7.1]
  3    29 ms    36 ms    29 ms  gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
  4    26 ms    79 ms    39 ms  0.xe-5-1-0.gw.pao1.sonic.net [69.12.211.1]
  5    38 ms    39 ms    39 ms  xe-1-0-6.ar1.pao1.us.nlayer.net [69.22.130.85]
  6    32 ms    35 ms    39 ms  ae0-90g.cr1.pao1.us.nlayer.net [69.22.153.18]
  7    38 ms    39 ms    29 ms  ae1-70g.cr1.sjc1.us.nlayer.net [69.22.143.165]
  8     *        *        *     Request timed out.
  9   100 ms   109 ms   128 ms  xe-0-0-1.cr1.nyc2.us.nlayer.net [69.22.142.86]
 10   107 ms    99 ms   106 ms  as8001.xe-1-3-1-3654.cr1.nyc2.us.nlayer.net [69.31.34.178]
 11   110 ms    99 ms   105 ms  0.e1-4.tbr1.oct.nac.net [209.123.10.122]
 12   104 ms   108 ms    99 ms  vlan804.esd1.oct.nac.net [209.123.10.2]
 13   105 ms   109 ms   109 ms  www.dslreports.com [209.123.109.175]
 

High first hop latency is probably introduced by the switch connected between the modem (ADSL2+) and the router; done to facilitate connecting with the modem for stats.

Second hop latency is due to the data path setting on the ADSL2+ modem.

Final latency is typical for a coast-to-coast trace with the DSL latency.

Your trace originates from Texas; your final latency is about what I would expect for a Texas to East Coast trace. Could you post a trace route to a problem server?

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum


mackey
Premium
join:2007-08-20
kudos:13
reply to warlock56
traceroute to dslreports.com (209.123.109.175), 30 hops max, 60 byte packets
 1  192.168.10.254 (192.168.10.254)  0.195 ms  0.114 ms  0.098 ms
 2  cpe-172-248-208-1.socal.res.rr.com (172.248.208.1)  979.261 ms  979.960 ms  979.898 ms
 3  tge0-7-0-4.vnnzca24-cer01.socal.rr.com (76.166.5.125)  8.905 ms  9.661 ms  15.400 ms
 4  agg11.vnnycajz-ccr01.socal.rr.com (72.129.14.96)  18.862 ms  19.860 ms  19.679 ms
 5  agg29.lsancarc-ccr01.socal.rr.com (72.129.13.0)  20.624 ms  21.385 ms  21.222 ms
 6  bu-ether16.lsancarc0yw-bcr00.tbone.rr.com (66.109.6.102)  22.030 ms  20.803 ms  21.589 ms
 7  107.14.19.138 (107.14.19.138)  13.952 ms ae-0-0.pr0.lax00.tbone.rr.com (66.109.6.135)  14.620 ms  14.379 ms
 8  66.109.9.122 (66.109.9.122)  14.345 ms  14.204 ms  12.917 ms
 9  vlan90.csw4.LosAngeles1.Level3.net (4.69.144.254)  93.708 ms vlan80.csw3.LosAngeles1.Level3.net (4.69.144.190)  93.404 ms vlan90.csw4.LosAngeles1.Level3.net (4.69.144.254)  92.054 ms
10  ae-73-73.ebr3.LosAngeles1.Level3.net (4.69.137.37)  93.120 ms ae-63-63.ebr3.LosAngeles1.Level3.net (4.69.137.33)  92.922 ms ae-83-83.ebr3.LosAngeles1.Level3.net (4.69.137.41)  89.298 ms
11  ae-3-3.ebr1.SanJose1.Level3.net (4.69.132.9)  94.307 ms  94.831 ms  94.635 ms
12  ae-2-2.ebr2.NewYork1.Level3.net (4.69.135.186)  94.938 ms  94.765 ms  95.118 ms
13  ae-82-82.csw3.NewYork1.Level3.net (4.69.148.42)  104.764 ms  88.328 ms ae-62-62.csw1.NewYork1.Level3.net (4.69.148.34)  93.890 ms
14  ae-1-60.edge8.NewYork1.Level3.net (4.69.155.15)  93.664 ms ae-2-70.edge8.NewYork1.Level3.net (4.69.155.79)  93.320 ms ae-4-90.edge8.NewYork1.Level3.net (4.69.155.207)  92.136 ms
15  NETACCESS.edge8.NewYork1.Level3.net (4.31.30.38)  91.427 ms  93.097 ms  92.814 ms
16  0.e1-4.tbr2.mmu.nac.net (209.123.10.77)  128.062 ms 0.e1-1.tbr2.ewr.nac.net (209.123.10.133)  129.088 ms 0.e1-4.tbr2.mmu.nac.net (209.123.10.77)  129.905 ms
17  0.e1-1.tbr2.oct.nac.net (209.123.10.21)  125.866 ms 0.e1-4.tbr2.oct.nac.net (209.123.10.126)  122.845 ms  133.400 ms
18  vlan808.esd1.oct.nac.net (209.123.10.42)  141.192 ms  148.614 ms  148.349 ms
19  www.dslreports.com (209.123.109.175)  110.116 ms  117.708 ms  115.651 ms
 

2 cpe-172-248-208-1.socal.res.rr.com (172.248.208.1) 979.261 ms 979.960 ms 979.898 ms
Looks like my node is a tad loaded tonight...

/M

toolman25

join:2012-11-19
Cincinnati, OH
Reviews:
·Cincinnati Bell
reply to warlock56
Tracing route to www.dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 * * * Request timed out.
2 16 ms 13 ms 14 ms ae0-1128.cr02.dytnoh55.swo.rr.com [65.25.147.24]

3 61 ms 21 ms 23 ms network-065-029-001-046.midwest.rr.com [65.29.1.
46]
4 28 ms 38 ms 30 ms ae-3-0.cr0.dca20.tbone.rr.com [66.109.6.70]
5 27 ms 36 ms 27 ms so-1-1-1.a0.alb75.tbone.rr.com [66.109.1.49]
6 40 ms 40 ms 42 ms ash-bb1-link.telia.net [80.239.132.169]
7 63 ms 62 ms 67 ms ash-bb3-link.telia.net [80.91.248.158]
8 68 ms 66 ms 65 ms nyk-bb1-link.telia.net [213.155.130.76]
9 68 ms 73 ms 83 ms nyk-b3-link.telia.net [80.91.248.174]
10 70 ms 69 ms 69 ms netaccess-tic-133837-nyk-b3.c.telia.net [213.248
.99.90]
11 69 ms 69 ms 69 ms 0.e1-4.tbr1.mmu.nac.net [209.123.10.101]
12 34 ms 36 ms 36 ms 0.e1-1.tbr1.oct.nac.net [209.123.10.17]
13 67 ms * 67 ms vlan804.esd1.oct.nac.net [209.123.10.2]
14 40 ms 39 ms 39 ms www.dslreports.com [209.123.109.175]

Trace complete.

C:\Users\Isaiah>

scififan68

join:2010-10-02
Fremont, NE
Reviews:
·Time Warner Cable
reply to warlock56
Tracing route to www.dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 44 ms 26 ms 31 ms cpe-76-84-96-1.neb.res.rr.com [76.84.96.1]
3 10 ms 11 ms 12 ms gig2-35.frmnne01-rtr1.neb.rr.com [76.85.222.5]
4 16 ms 12 ms 12 ms tge10-0-0.lnclne03-mx91.neb.rr.com [76.85.221.129]
5 39 ms 30 ms 12 ms ae1.lnclne03-mx92.neb.rr.com [76.85.221.114]
6 19 ms 12 ms 12 ms ae0.lnclne04-mx91.neb.rr.com [76.85.221.118]
7 13 ms 12 ms 13 ms ae1.lnclne04-mx92.neb.rr.com [76.85.221.122]
8 11 ms 12 ms 11 ms ae0.lnclne00-mx41.neb.rr.com [76.85.221.126]
9 36 ms 39 ms 31 ms 66.109.1.64
10 * 33 ms 31 ms 107.14.17.147
11 53 ms 60 ms 59 ms ae18.edge2.Chicago2.Level3.net [4.68.111.33]
12 54 ms 55 ms 54 ms vl-3502-ve-116.ebr1.Chicago2.Level3.net [4.69.158.6]
13 58 ms 77 ms 63 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
14 59 ms 54 ms 54 ms ae-2-2.ebr2.NewYork2.Level3.net [4.69.132.66]
15 52 ms 54 ms 56 ms ae-46-46.ebr2.NewYork1.Level3.net [4.69.201.29]
16 54 ms 60 ms 57 ms ae-62-62.csw1.NewYork1.Level3.net [4.69.148.34]
17 55 ms 56 ms 53 ms ae-1-60.edge8.NewYork1.Level3.net [4.69.155.15]
18 53 ms 54 ms 55 ms NETACCESS.edge8.NewYork1.Level3.net [4.31.30.38]
19 114 ms 89 ms 96 ms 0.e1-1.tbr2.ewr.nac.net [209.123.10.133]
20 86 ms 88 ms 86 ms 0.e1-4.tbr2.oct.nac.net [209.123.10.126]
21 53 ms 60 ms 60 ms vlan808.esd1.oct.nac.net [209.123.10.42]
22 88 ms 85 ms * www.dslreports.com [209.123.109.175]
23 94 ms 86 ms 95 ms www.dslreports.com [209.123.109.175]

Interesting how Socal is 1000 miles+ west of me and yet the ping has only has a small difference, 86-96ms vs 110-117ms.

Mele20
Premium
join:2001-06-05
Hilo, HI
kudos:5
reply to warlock56
Click for full size
For many years, tracert to dslr from the Big Island averaged 140ms. I own Ping Plotter Pro since 2005 and Ping Plotter regular version since 2001 so I know.

Recently, it has been obscene in the evenings sometimes pinging WAY ABOVE 200ms! The problem is t-bone and Level3 routers in that god-awful mess in LA. I hate corporate TWC for deliberately screwing Hawaii back in 2005. When the RDC was at Mililani, Oahu we surfaced at San Jose NOT Orange RR. Over all speeds back then were nothing like now but the routing was so superior to what we have since corporate punished Oceanic and took the RDC away and put at Orange RR that we were better off with low speeds but the best routing.

Note that we STILL route to San Jose but since the forced move of the RDC we now have to transit the crap in LA first. I now see ping times to LA that are higher than ping times for many, many years were all the way to dslr in New York. Pathetic.

--
When governments fear people, there is liberty. When the people fear the government, there is tyranny. Thomas Jefferson

xQuestx

join:2001-05-15
Bar Harbor, ME
Target Name: www.dslreports.com
IP: 209.123.109.175
Date/Time: 6/5/2013 7:36:00 AM to 6/5/2013 7:36:09 AM

1 0 ms 1 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms RT-N65R [192.168.2.1]
2 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms unknown [192.168.1.2]
3 6 ms 7 ms 10 ms 6 ms 7 ms 7 ms 7 ms 7 ms 7 ms 7 ms [10.230.128.1]
4 8 ms 9 ms 8 ms 8 ms 9 ms 9 ms 9 ms 9 ms 9 ms 9 ms g5-2-15.lttnnhca-rtr001.ne.northeast.rr.com [24.31.154.238]
5 12 ms 13 ms 12 ms 12 ms 17 ms 13 ms 13 ms 13 ms 13 ms 11 ms g10-6-3-0.ptldmehx-rtr001.ne.northeast.rr.com [204.210.69.206]
6 35 ms 35 ms 30 ms 32 ms 35 ms 36 ms 38 ms 32 ms 33 ms 35 ms rdc-204-210-69-49.ne.northeast.rr.com [204.210.69.49]
7 33 ms 34 ms 33 ms 30 ms 33 ms 34 ms 32 ms 34 ms 32 ms 34 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
8 30 ms 31 ms 30 ms 32 ms 40 ms 31 ms 32 ms 57 ms 31 ms 29 ms [107.14.17.169]
9 36 ms 42 ms 33 ms 34 ms 35 ms 32 ms 35 ms 34 ms 33 ms 37 ms xe-5-0-6.ar2.ewr1.us.nlayer.net [69.31.94.57]
10 31 ms 31 ms 31 ms 31 ms 32 ms 31 ms 32 ms 32 ms 32 ms 32 ms ae7-40g.cr1.nyc2.us.nlayer.net [69.31.34.126]
11 31 ms 32 ms 38 ms 31 ms 32 ms 31 ms 32 ms 32 ms 32 ms 40 ms as8001.xe-1-3-1-3654.cr1.nyc2.us.nlayer.net [69.31.34.178]
12 33 ms 32 ms 33 ms 31 ms 33 ms 31 ms 33 ms 33 ms 33 ms N/A 0.e1-4.tbr1.oct.nac.net [209.123.10.122]
13 32 ms 32 ms 32 ms 31 ms 33 ms 32 ms 33 ms 33 ms 33 ms N/A vlan804.esd1.oct.nac.net [209.123.10.2]
14 31 ms 38 ms 32 ms 31 ms 32 ms 32 ms 32 ms 33 ms 33 ms 33 ms www.dslreports.com [209.123.109.175]

Ping statistics for www.dslreports.com
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 31ms, Maximum = 38ms, Average = 32ms


AMDUSER
Premium
join:2003-05-28
Earth,
kudos:1
Reviews:
·AT&T U-Verse
·Time Warner Cable
reply to warlock56
Here is a tracert from an At&t [IP-DSL] connection:
  1     3 ms     2 ms     8 ms  DD-WRT [192.168.1.1]
  2     2 ms     2 ms     2 ms  dsldevice.att.net [192.168.1.254]
  3    30 ms    21 ms    23 ms 198.81.129.107.lightspeed.milwwi.sbcglobal.net [198.81.129.107]
  4    25 ms     *        *     71.144.192.106
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    23 ms     *       20 ms  12.83.79.141
  8    29 ms    31 ms    31 ms  gar13.cgcil.ip.att.net [12.122.132.121]
  9    37 ms    28 ms    29 ms  chi-bb1-link.telia.net [213.248.87.253]
 10    82 ms    93 ms    50 ms  nyk-bb2-link.telia.net [213.155.131.242]
 11    50 ms    50 ms    50 ms  nyk-b3-link.telia.net [80.91.247.21]
 12    51 ms    51 ms    50 ms  netaccess-tic-133837-nyk-b3.c.telia.net [213.248.99.90]
 13    51 ms    51 ms    52 ms  0.e1-1.tbr1.ewr.nac.net [209.123.10.129]
 14    51 ms    58 ms    60 ms  0.e1-4.tbr1.oct.nac.net [209.123.10.122]
 15    54 ms    53 ms     *     vlan804.esd1.oct.nac.net [209.123.10.2]
 16    54 ms    54 ms    58 ms  www.dslreports.com [209.123.109.175]
 

-Note: the 198.81.129.107 location is not my IP address....


BIGMIKE
Premium
join:2002-06-07
Westminster, CA
reply to warlock56
Target Name: dslreports.com
IP: 209.123.109.175
Date/Time: 6/5/2013 7:17:10 AM

1 18 ms 26 ms N/A cpe-**-******-1.socal.res.rr.com [72.130.24.1]
2 N/A 13 ms 12 ms tge7-3.wmnsca15-cer02.socal.rr.com [76.166.13.117]
3 N/A 19 ms 14 ms tge0-8-0-10.grgvcabt-ccr02.socal.rr.com [72.129.29.168]
4 19 ms 18 ms N/A agg23.tustcaft-ccr01.socal.rr.com [72.129.29.2]
5 13 ms * 24 ms [107.14.19.30]
6 20 ms * 18 ms [107.14.19.67]
7 21 ms 17 ms 17 ms [66.109.9.122]
8 86 ms * 85 ms vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62]
9 89 ms 87 ms 96 ms ae-63-63.ebr3.LosAngeles1.Level3.net [4.69.137.33]
10 87 ms * N/A ae-3-3.ebr1.SanJose1.Level3.net [4.69.132.9]
11 92 ms 88 ms 91 ms ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186]
12 N/A 91 ms 86 ms ae-82-82.csw3.NewYork1.Level3.net [4.69.148.42]
13 N/A 87 ms N/A ae-3-80.edge8.NewYork1.Level3.net [4.69.155.143]
14 N/A 89 ms 87 ms NETACCESS.edge8.NewYork1.Level3.net [4.31.30.38]
15 93 ms 92 ms 98 ms 0.e1-1.tbr2.ewr.nac.net [209.123.10.133]
16 N/A 97 ms N/A 0.e1-4.tbr2.oct.nac.net [209.123.10.126]
17 95 ms * N/A vlan808.esd1.oct.nac.net [209.123.10.42]
18 94 ms 99 ms 91 ms www.dslreports.com [209.123.109.175]

Ping statistics for dslreports.com
Packets: Sent = 3, Received = 3, Lost = 0 (0.0%)
Round Trip Times: Minimum = 91ms, Maximum = 99ms, Average = 94ms


BIGMIKE
Premium
join:2002-06-07
Westminster, CA
reply to warlock56
94 ping

Happydude32
Premium
join:2005-07-16
kudos:1
reply to warlock56
How's this look? :)

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
 
C:\Users\Steve>tracert dslreports.com
 
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  [192.168.10.1]
  2     6 ms     7 ms     7 ms  10.109.0.1
  3     8 ms     8 ms     7 ms  gig8-4.faptnyalrtr002.wny.northeast.rr.com [24.93.12.27]
  4    24 ms    23 ms    23 ms  rdc-72-230-153-184.wny.east.twcable.com [72.230.153.184]
  5    11 ms    10 ms     9 ms  rdc-72-230-153-80.wny.east.twcable.com [72.230.153.80]
  6    28 ms    31 ms    23 ms  rdc-72-230-153-243.wny.east.twcable.com [72.230.153.243]
  7    24 ms    27 ms    23 ms  ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72]
  8    23 ms    26 ms    22 ms  ae0.pr1.chi10.tbone.rr.com [107.14.17.192]
  9    23 ms    23 ms    23 ms  chi-bb1-link.telia.net [213.248.66.193]
 10    59 ms    31 ms    23 ms  chi-bb1-link.telia.net [80.91.246.168]
 11    37 ms    35 ms    35 ms  nyk-bb2-link.telia.net [80.91.249.111]
 12    37 ms    40 ms    35 ms  nyk-b3-link.telia.net [80.91.247.21]
 13    36 ms    37 ms    35 ms  netaccess-tic-133837-nyk-b3.c.telia.net [213.248.99.90]
 14    39 ms    37 ms    36 ms  0.e1-4.tbr1.mmu.nac.net [209.123.10.101]
 15    37 ms    37 ms    37 ms  0.e1-1.tbr1.oct.nac.net [209.123.10.17]
 16    37 ms    37 ms    37 ms  vlan804.esd1.oct.nac.net [209.123.10.2]
 17    38 ms    38 ms    36 ms  www.dslreports.com [209.123.109.175]
 
Trace complete.
 


NormanS
I gave her time to steal my mind away
Premium,MVM
join:2001-02-14
San Jose, CA
kudos:12
Reviews:
·SONIC.NET
·Pacific Bell - SBC
reply to AMDUSER
said by AMDUSER:

-Note: the 198.81.129.107 location is not my IP address....

Of course not; the first public IP hop is never is the IP address of the tracer. What is odd in your case is that the the host name, "*.lightspeed.milwwi.sbcglobal.net", screams IP-DSLAM for an AT&T U-verse HSI connection; but ARIN claims the IP address is assigned to the CIA!
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum


NormanS
I gave her time to steal my mind away
Premium,MVM
join:2001-02-14
San Jose, CA
kudos:12
Reviews:
·SONIC.NET
·Pacific Bell - SBC
reply to Mele20
said by Mele20:

For many years, tracert to dslr from the Big Island averaged 140ms.

I question that claim. As the crow flies along a great circle, New York is ~2,490 miles east of San Jose. My trace routes in that direction averaged ~90 ms for ADSL on Fastpath.

As the crow flies along a great circle, San Jose is ~2,370 east of the "Big Island", so I am guessing ~90 ms on that route, as well. So probably ~180 ms overall.

Of course, Hawaii to Orange to San Jose to New York is ~215 miles longer than Hawaii to San Jose to New York, so I would expect higher latency on that route, as well.

Recently, it has been obscene in the evenings sometimes pinging WAY ABOVE 200ms! The problem is t-bone and Level3 routers in that god-awful mess in LA. I hate corporate TWC for deliberately screwing Hawaii back in 2005. When the RDC was at Mililani, Oahu we surfaced at San Jose NOT Orange RR. Over all speeds back then were nothing like now but the routing was so superior to what we have since corporate punished Oceanic and took the RDC away and put at Orange RR that we were better off with low speeds but the best routing.

Note that we STILL route to San Jose but since the forced move of the RDC we now have to transit the crap in LA first. I now see ping times to LA that are higher than ping times for many, many years were all the way to dslr in New York. Pathetic.

It looks like the RR "T-bone" is the worst part of the route. But I don't see Level 3 as a problem. Even if Level 3 routed you east out of Los Angeles, you'd still have to make a 300+ mile northing. LA-SJ-DEN-NY, LA-DFW-DEN-NY, or LA-DFW-ATL-NY; it is mostly the same on Level 3. The submarine termination in Socal is clearly killing you. Unfortunately, TWC only meets Tier 1 transit in San Jose; they would not, likely, have an RDC in Comcast territory. When I trace back to Hawaii, I route through nLayer in Palo Alto to RR "T-bone" in San Jose, then on the "T-bone" to Los Angeles, before turning west under the Pacific Ocean.
Tracing route to cpe-70-95-176-1.hawaii.res.rr.com [70.95.176.1]
over a maximum of 30 hops:
 
  1     4 ms     9 ms     9 ms  Chihiro [192.168.102.1]
  2    34 ms    31 ms    33 ms  173-228-7-1.dsl.static.sonic.net [173.228.7.1]
  3    31 ms    39 ms    34 ms  gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
  4    31 ms    35 ms    32 ms  0.xe-5-1-0.gw.pao1.sonic.net [69.12.211.1]
  5    30 ms    39 ms    38 ms  xe-1-0-6.ar1.pao1.us.nlayer.net [69.22.130.85]
  6    33 ms    26 ms    32 ms  as7843.xe-2-0-1.ar1.pao1.us.nlayer.net [69.22.153.122]
  7    43 ms    35 ms    48 ms  ae-2-0.cr0.sjc10.tbone.rr.com [66.109.6.142]
  8    43 ms    49 ms    47 ms  bu-ether13.lsancarc0yw-bcr00.tbone.rr.com [66.109.6.7]
  9    63 ms    49 ms    49 ms  66.109.6.213
 10   156 ms   159 ms   158 ms  agg1.milnhixd-ccr01.hawaii.rr.com [72.129.45.1]
 11   165 ms   158 ms   168 ms  agg10.kmlahi07-ccr01.hawaii.rr.com [72.129.45.41]
 12   165 ms   169 ms   168 ms  tge9-1.hilihiee-cer01.hawaii.rr.com [72.129.46.163]
 13   165 ms   169 ms   169 ms  cpe-70-95-176-1.hawaii.res.rr.com [70.95.176.1]
 
Trace complete.
 
This trace runs to a North S.F. Bay Area location from my San Jose residence before routing back south to Palo Alto; adds about 115 miles of latency before joining with nLayer transit.

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum

Mele20
Premium
join:2001-06-05
Hilo, HI
kudos:5
Click for full size
No. Speed of light is around 40-43ms and a good connection from Oahu to the West Coast (and from the other islands) can be around 10-15ms more. For me, it is usually 56-60ms to the West Coast (and higher during prime usage hours). I've had it as low as 50ms to the West Coast. The problem is there in Los Angeles area AFTER arriving there from Hawaii. There is a many year, longstanding bottleneck in the LA area sometimes with tbone routers and sometimes with Level 3 routers and sometimes both. When things are working well with no bottleneck there, ping is back to 135-145ms to dslr (assuming no problems from LA to nac.net and usually it is tbone out of Orange RR connecting to Level 3 in Los Angeles and staying on Level 3 all the way to nac.net).

You are seeing why I said TWC corporate screwed Hawaii deliberately when they removed the RDC from Oceanic's hands and stuck it rudely at Orange RR where Orange was offended and we were we very upset also. When the RDC was at Oceanic, we landed in San Jose area totally avoiding the mess in Southern California.

It is 5:26PM here and this is an excellent time for me accessing websites (5-6PM). I just switched to the XP computer and then did a direct connection as I am trying to diagnose frequent DNS errors for the past week (not just ones here due to the DDoS of EasyDNS). Ping to dslreports is at 137ms on Ping Plotter Pro. An hour ago, on the Win 8 machine with the Linksy router - (Sam Knows router has been disabled for the time being) Ping Plotter was showing 185ms to dslreports. It will be interesting to see on XP computer with a direct modem connection later, during prime usage time, what ping I get to dslreports. (Also will be interesting to see if the frequent DNS errors stop).
--
When governments fear people, there is liberty. When the people fear the government, there is tyranny. Thomas Jefferson


NormanS
I gave her time to steal my mind away
Premium,MVM
join:2001-02-14
San Jose, CA
kudos:12
Reviews:
·SONIC.NET
·Pacific Bell - SBC
Odd, your PP result is 139 ms average, Hawaii to Level 3 Los Angeles, but 136 ms average Hawaii to New York? That's a transit latency of -3 ms average! Unless TWC has learned how to apply Thiotimoline to electrons in fiber, that is an anomalous result.

A couple of concessions:

• Transoceanic cable is probably more direct than trans continental cable; so the U.S. West Coast is probably closer to Hawaii, in wire (fiber, actually) miles than the East Coast of the United States.

• The Orange RR RDC is probably ~450 fiber miles from San Jose; so added latency for that leg.

But all things being equal, I don't believe a 5 ms hop from Hawaii to California is possible, even for light in glass. I could buy a 52 ms latency (your hop 2 to your hop 3) for a transoceanic cable.

I can also see ~40 ms added for Orange to San Jose. That is still ~60 ms under the Pacific Ocean, ~40 ms up the West Coast from Orange to San Jose, and ~90 ms from San Jose to the East Cost. Or, backing out the Socal routing, and going direct through San Jose, I can see ~150 ms on a good day. So I will concede your claim for past latency.

I also see apparent congestion between TWC (T-bone) and Level 3 in Los Angeles. Obviously, you won't get comparable latency to the past due to the West Cost routing. But I would expect ~180 ms to be your new normal, overall.

San Jose, California to New York.

San Jose, California to Hawaii.

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum


DrDrew
That others may surf
Premium
join:2009-01-28
SoCal
kudos:17

1 edit
The RDC location and routing are two separate things.

RDC is where some main servers are, it's a Regional Data Center after all. Nothing actually routes through the RDC unless it's contacting those servers.

Routing changed years ago when ATDN (AOLs network) was dropped in favor of an in-house TWC backbone network. TWC has 2 peering/transit points in the Los Angeles area. The TWC connection from Hawaii comes into them and can leave the network from that same location, the RDC in Orange is never touched.

TWC also has 2 peering/transit points in the San Jose area.

»www.peeringdb.com/view.php?asn=7843
--
Two is one, one is none. If it's important, have a back up... 99.999% availability just isn't enough sometimes.


Suit Up

join:2003-07-21
Los Angeles, CA
reply to warlock56
traceroute to dslreports.com (209.123.109.175), 30 hops max, 38 byte packets
 1  cpe-76-91-96-1.socal.res.rr.com (76.91.96.1)  26.542 ms  18.796 ms  21.344 ms
 2  tge7-1.wlvgcabn-cer01.socal.rr.com (76.166.19.161)  8.988 ms  8.517 ms  9.159 ms
 3  tge0-8-0-8.vnnycajz-ccr01.socal.rr.com (72.129.13.96)  12.968 ms  12.683 ms  15.741 ms
 4  agg29.lsancarc-ccr01.socal.rr.com (72.129.13.0)  19.505 ms  17.670 ms  15.939 ms
 5  bu-ether16.lsancarc0yw-bcr00.tbone.rr.com (66.109.6.102)  13.987 ms  18.429 ms  15.736 ms
 6  ae-0-0.pr0.lax00.tbone.rr.com (66.109.6.135)  11.558 ms  19.500 ms  107.14.19.86 (107.14.19.86)  13.122 ms
 7  66.109.9.122 (66.109.9.122)  12.631 ms  15.051 ms  14.523 ms
 8  vlan90.csw4.LosAngeles1.Level3.net (4.69.144.254)  85.358 ms  86.306 ms  86.099 ms
 9  ae-93-93.ebr3.LosAngeles1.Level3.net (4.69.137.45)  86.050 ms  ae-73-73.ebr3.LosAngeles1.Level3.net (4.69.137.37)  84.036 ms  ae-63-63.ebr3.LosAngeles1.Level3.net (4.69.137.33)  86.546 ms
10  ae-3-3.ebr1.SanJose1.Level3.net (4.69.132.9)  84.404 ms  84.468 ms  86.149 ms
11  ae-2-2.ebr2.NewYork1.Level3.net (4.69.135.186)  86.317 ms  84.675 ms  85.955 ms
12  ae-82-82.csw3.NewYork1.Level3.net (4.69.148.42)  99.380 ms  ae-62-62.csw1.NewYork1.Level3.net (4.69.148.34)  91.201 ms  ae-92-92.csw4.NewYork1.Level3.net (4.69.148.46)  84.964 ms
13  ae-2-70.edge8.NewYork1.Level3.net (4.69.155.79)  85.242 ms  ae-3-80.edge8.NewYork1.Level3.net (4.69.155.143)  84.885 ms  ae-1-60.edge8.NewYork1.Level3.net (4.69.155.15)  84.407 ms
14  NETACCESS.edge8.NewYork1.Level3.net (4.31.30.38)  87.317 ms  87.759 ms  85.152 ms
15  0.e1-4.tbr2.mmu.nac.net (209.123.10.77)  91.038 ms  91.628 ms  91.454 ms
16  0.e1-1.tbr2.oct.nac.net (209.123.10.21)  93.867 ms  95.896 ms  92.323 ms
17  *  *  *
18  *  *  *
19  *  *  *
20  *  *  *
21  *  *  *
22  *  *  *
23  *  *  *
24  *  *  *
25  *  *  *
26  *  *  *
27  *  *  *
28  *  *  *
29  *  *  *
30  *  *  *
 
How come I can't get anything after the 16th hop, and everybody else can? Weird. I even tried the "ICMP ECHO" and "TCP SYN" options and that didn't help.


motorola870

join:2008-12-07
Arlington, TX
kudos:4
reply to warlock56
said by warlock56:

Lately I've been playing a some fps games on occasion. I'd been off of them for a couple of years now actually; I don't know what made me decide to try them again.

So anyway one thing I've noticed in different fps games is my ping time is typically at least in the 100ms range. When was on at&t my ping time was usually better, probably around 60ms range. There are still some servers that have better ping response than others, but by and large most of them are on the high side, which leads me to believe the routing TWC is using may be causing the lag.

So I'm posting a traceroute from my computer to dslreports.com that was taken just a few minutes ago. I'm curious to know, especially from other users who live in the same area, what your routing looks like.

nice were on the same CMTS

Tracing route to www.dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 22 ms 35 ms 29 ms cpe-173-175-192-1.tx.res.rr.com [173.175.192.1]

2 14 ms 10 ms 11 ms tge7-2.dllatx34-er02.texas.rr.com [70.125.218.29
]
3 13 ms 27 ms 13 ms tge0-8-0-5.dllatx34-tr02.texas.rr.com [24.175.38
.88]
4 25 ms 19 ms 14 ms agg23.dllatx10-cr02.texas.rr.com [24.175.36.232]

5 17 ms 15 ms 15 ms agg21.hstntxl3-cr01.texas.rr.com [24.175.49.8]
6 20 ms 15 ms 16 ms 107.14.17.138
7 17 ms 20 ms 20 ms 107.14.17.141
8 17 ms 16 ms 15 ms 107.14.16.186
9 49 ms 54 ms 48 ms vlan90.csw4.Dallas1.Level3.net [4.69.145.254]
10 51 ms 51 ms 48 ms ae-92-92.ebr2.Dallas1.Level3.net [4.69.151.166]

11 49 ms 51 ms 50 ms ae-3-3.ebr2.NewYork1.Level3.net [4.69.137.122]
12 67 ms 50 ms 51 ms ae-82-82.csw3.NewYork1.Level3.net [4.69.148.42]

13 49 ms 51 ms 69 ms ae-3-80.edge8.NewYork1.Level3.net [4.69.155.143]

14 50 ms 50 ms 50 ms NETACCESS.edge8.NewYork1.Level3.net [4.31.30.38]

15 59 ms 60 ms 57 ms 0.e1-4.tbr2.mmu.nac.net [209.123.10.77]
16 58 ms 57 ms 58 ms 0.e1-1.tbr2.oct.nac.net [209.123.10.21]
17 57 ms 58 ms 56 ms vlan808.esd1.oct.nac.net [209.123.10.42]
18 63 ms 59 ms 59 ms www.dslreports.com [209.123.109.175]

Trace complete.

Mele20
Premium
join:2001-06-05
Hilo, HI
kudos:5
reply to NormanS
Click for full size
In the past about 3 months, there have been big changes in routing. I used to ping "www.mit.edu" ever since I got RR in 2001 because the head computer tech at Oceanic here told me he thought it was super cool to ping that site on the East Coast (partly because it is mit and partly because it is internet backbone. So, all these years he and I and others have pinged that site). I about fell off my chair a few weeks ago when I started Ping Plotter (hadn't run it for several weeks) to mit.edu and the routing stopped in Los Angeles! Only 8 hops now to mit.edu! It pings usually now at about 70ms. It's on Akamai now. At the moment, it is pinging at 116ms and tbone in LA (the hop just before Akamai) is showing 8% packet loss but it is not affecting the final hop.

As for dslreports.com pinged either via ICMP engine or TCP engine on Ping Plotter, BIG changes recentlly in the routing. It used to be from Hawaii to Orange RR (still is.. I think Drew may have it wrong - we always go through or, appear at least, to go through Orange RR server), then onto Level 3 to Washington DC and then Level 3 to Newark and then to nac.net. The recent change has been after Orange RR, to tbone in Los Angeles, then Level 3 in Los Angeles, then Level 3 in SanJose, Level 3 in NY, then nac.net.

My screenshot is from last Nov right after I got the new computer and was having connection problems (I still had the 8 year old DOCSIS 2 modem then) but I'm posting it to show the difference in routing from then and currently for dslreports. Hops 7 and 8 are Southern Cal Road Runner and you would expect hop 12 router to be on the East Coast as you can see the big change in latency between hops 11 and 12. However, that router says its a Level3 one in Los Angeles.

Until recently, the large latency change would show via commandline tracert or Ping Plotter in the appropriate places (East coast hop not Los Angeles one) but not for awhile now. Even the Hawaii portions of tracert are not too clear anymore. Hop 5 is Hawaii RR but after it has landed at Orange RR. Of course, there is a large latency change between Los Angles/San Jose and New York but it has not shown correctly for several months now on both traceroute and Ping Plotter on both XP and Win 8 computers.

My main point here though is final ping to dslreports.com is around 135ms ideally and has been for many, many years now. There have been periods when it was higher (around 180ms) but that would get fixed eventually. Ping to Orange RR is always LOWER by about 10-15ms if you subscribe to any tier above Standard. Oceanic told me that is deliberate.
--
When governments fear people, there is liberty. When the people fear the government, there is tyranny. Thomas Jefferson


warlock56
Premium
join:2002-07-31
Arlington, TX
reply to motorola870
said by motorola870:

said by warlock56:

Lately I've been playing a some fps games on occasion. I'd been off of them for a couple of years now actually; I don't know what made me decide to try them again.

So anyway one thing I've noticed in different fps games is my ping time is typically at least in the 100ms range. When was on at&t my ping time was usually better, probably around 60ms range. There are still some servers that have better ping response than others, but by and large most of them are on the high side, which leads me to believe the routing TWC is using may be causing the lag.

So I'm posting a traceroute from my computer to dslreports.com that was taken just a few minutes ago. I'm curious to know, especially from other users who live in the same area, what your routing looks like.

nice were on the same CMTS

Tracing route to www.dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 22 ms 35 ms 29 ms cpe-173-175-192-1.tx.res.rr.com [173.175.192.1]

2 14 ms 10 ms 11 ms tge7-2.dllatx34-er02.texas.rr.com [70.125.218.29
]
3 13 ms 27 ms 13 ms tge0-8-0-5.dllatx34-tr02.texas.rr.com [24.175.38
.88]
4 25 ms 19 ms 14 ms agg23.dllatx10-cr02.texas.rr.com [24.175.36.232]

5 17 ms 15 ms 15 ms agg21.hstntxl3-cr01.texas.rr.com [24.175.49.8]
6 20 ms 15 ms 16 ms 107.14.17.138
7 17 ms 20 ms 20 ms 107.14.17.141
8 17 ms 16 ms 15 ms 107.14.16.186
9 49 ms 54 ms 48 ms vlan90.csw4.Dallas1.Level3.net [4.69.145.254]
10 51 ms 51 ms 48 ms ae-92-92.ebr2.Dallas1.Level3.net [4.69.151.166]

11 49 ms 51 ms 50 ms ae-3-3.ebr2.NewYork1.Level3.net [4.69.137.122]
12 67 ms 50 ms 51 ms ae-82-82.csw3.NewYork1.Level3.net [4.69.148.42]

13 49 ms 51 ms 69 ms ae-3-80.edge8.NewYork1.Level3.net [4.69.155.143]

14 50 ms 50 ms 50 ms NETACCESS.edge8.NewYork1.Level3.net [4.31.30.38]

15 59 ms 60 ms 57 ms 0.e1-4.tbr2.mmu.nac.net [209.123.10.77]
16 58 ms 57 ms 58 ms 0.e1-1.tbr2.oct.nac.net [209.123.10.21]
17 57 ms 58 ms 56 ms vlan808.esd1.oct.nac.net [209.123.10.42]
18 63 ms 59 ms 59 ms www.dslreports.com [209.123.109.175]

Trace complete.

I was mainly curious of people in the north Texas area what their routing looked like. Since you're the first to respond, and our routing looks similar, I'll ask this: does it look to you like all traffic gets routed to some point in Houston before coming back up here again and then being routed outbound to the final destination?
--
The moment the idea is admitted into society, that property is not as sacred as the laws of God, and that there is not a force of law and public justice to protect it, anarchy and tyranny commence. -John Adams, 1787

SanAntonioTx
Premium
join:2008-07-18
Venice, CA
Reviews:
·Verizon Wireless..
·Time Warner Cable
·Clearwire Wireless
reply to warlock56
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 1 ms 1 ms 7 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 15 ms 9 ms tge7-1.snantx6800-er01.texas.rr.com [24.28.134.1
44]
4 29 ms 46 ms 13 ms tge0-11-0-6.snantx6000-cr01.texas.rr.com [24.175
.33.232]
5 19 ms 23 ms 24 ms 24.175.32.146
6 36 ms 57 ms 38 ms ae-4-0.cr0.dfw10.tbone.rr.com [66.109.6.88]
7 22 ms 39 ms 24 ms ae0.pr1.dfw10.tbone.rr.com [107.14.17.232]
8 209 ms 24 ms 23 ms xe-2-0-3.ar1.dfw1.us.nlayer.net [69.31.63.1]
9 24 ms 28 ms 188 ms ae0-50g.cr1.dfw1.us.nlayer.net [69.31.63.125]
10 60 ms 82 ms 64 ms xe-8-3-0.cr1.nyc2.us.nlayer.net [69.22.142.141]
11 64 ms 64 ms 65 ms 0.e1-4.tbr1.oct.nac.net [209.123.10.122]
12 68 ms 98 ms 65 ms vlan804.esd1.oct.nac.net [209.123.10.2]
13 82 ms 97 ms 133 ms www.dslreports.com [209.123.109.175]


DrDrew
That others may surf
Premium
join:2009-01-28
SoCal
kudos:17

2 edits
reply to Mele20
said by Mele20:

...in the routing. It used to be from Hawaii to Orange RR (still is.. I think Drew may have it wrong - we always go through or, appear at least, to go through Orange RR server), then onto Level 3 to Washington DC and then Level 3 to Newark and then to nac.net. The recent change has been after Orange RR, to tbone in Los Angeles, then Level 3 in Los Angeles, then Level 3 in SanJose, Level 3 in NY, then nac.net.

That is not Orange, that is Tustin (tustcaft). They are a few miles apart.

Also, you don't route through a server...

--
Two is one, one is none. If it's important, have a back up... 99.999% availability just isn't enough sometimes.

JPP
Extremist should be shot
Premium
join:2007-05-04
Falls Church, VA
reply to warlock56
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 7 ms 6 ms L100.WASHDC-VFTTP-91.verizon-gni.net [173.66.84.1]
3 13 ms 9 ms 7 ms G0-3-4-2.WASHDC-LCR-22.verizon-gni.net [130.81.48.252]
4 7 ms 6 ms 8 ms ae2-0.RES-BB-RTR1.verizon-gni.net [130.81.199.138]
5 7 ms 7 ms 7 ms 0.xe-3-1-0.BR2.IAD8.ALTER.NET [152.63.38.157]
6 10 ms 12 ms 9 ms ae17.edge1.washingtondc12.level3.net [4.68.62.137]
7 14 ms 14 ms 13 ms vl-3604-ve-228.ebr2.Washington12.Level3.net [4.69.158.46]
8 15 ms 14 ms 14 ms 4.69.201.65
9 16 ms 14 ms 14 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]
10 16 ms 13 ms 15 ms ae-1-60.edge8.NewYork1.Level3.net [4.69.155.15]
11 19 ms 19 ms 19 ms NETACCESS.edge8.NewYork1.Level3.net [4.31.30.38]
12 17 ms 19 ms 16 ms 0.e1-1.tbr2.ewr.nac.net [209.123.10.133]
13 17 ms 17 ms 17 ms 0.e1-4.tbr2.oct.nac.net [209.123.10.126]
14 17 ms 17 ms 15 ms vlan808.esd1.oct.nac.net [209.123.10.42]
15 17 ms 16 ms 17 ms www.dslreports.com [209.123.109.175]

Trace complete.


NormanS
I gave her time to steal my mind away
Premium,MVM
join:2001-02-14
San Jose, CA
kudos:12
Reviews:
·SONIC.NET
·Pacific Bell - SBC
reply to Mele20
My experience of geocodes in host names is that they are reasonably accurate, except after network renumbering; before the engineers change the names to match the new locations. For AS 7132 (ATTIS, formerly SBCIS), "snfcca" is San Francisco, "sntcca" is Santa Clara, and "pltnca" is Pleasanton. So I have to agree with DrDrew See Profile: That "tustcaft" is Tustin.

Please explain how MIT is a backbone. In any case, it seems obvious that MIT is using Akamai to store online content, which can then be delivered to users from the nearest server farms.

The difference between your November plot, and current plot, is the leg from Los Angeles to San Jose; will add ~40 ms to latency because the leg runs north, and sightly west before turning east. This adds a little over double the northward run from DC to New Jersey.

The anomalous leap in latency may be due to naming conventions. Network operators may name a local port for the distant router location if that port is dedicated to that location. So a port in DC, which is dedicated to receiving packets solely from an LA router, may show LA in the host name.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum


anon user

@rr.com
reply to warlock56
traceroute to dslreports.com (209.123.109.175), 64 hops max, 72 byte packets
1 cable-mac1.schnny52-ar4002.nyroc.rr.com (67.242.64.1) 62.728 ms 20.187 ms 70.722 ms
2 gig9-32.schnny52-rtr001.alb.northeast.rr.com (24.29.46.193) 15.709 ms 10.770 ms 13.070 ms
3 rdc-74-76-241-78.alb.northeast.rr.com (74.76.241.78) 13.101 ms 11.330 ms 12.465 ms
4 rdc-74-76-241-193.alb.northeast.rr.com (74.76.241.193) 31.698 ms 70.864 ms 64.803 ms
5 ae-5-0.cr0.nyc30.tbone.rr.com (66.109.6.74) 18.177 ms 22.513 ms 20.046 ms
6 107.14.17.169 (107.14.17.169) 18.360 ms 22.430 ms 24.186 ms
7 xe-5-0-6.ar2.ewr1.us.nlayer.net (69.31.94.57) 46.819 ms 40.533 ms 21.867 ms
8 ae7-40g.cr1.nyc2.us.nlayer.net (69.31.34.126) 21.466 ms 20.851 ms 21.673 ms
9 as8001.xe-1-3-1-3654.cr1.nyc2.us.nlayer.net (69.31.34.178) 41.242 ms 38.540 ms 44.681 ms
10 0.e1-4.tbr1.oct.nac.net (209.123.10.122) 22.908 ms 22.093 ms 25.372 ms
11 vlan804.esd1.oct.nac.net (209.123.10.2) 22.620 ms 21.831 ms 21.949 ms
12 www.dslreports.com (209.123.109.175) 22.174 ms 20.829 ms 19.512 ms


WiFiguru
To infinity... and beyond
Premium
join:2005-06-21
Irvine, CA
Reviews:
·DSL EXTREME
reply to warlock56
traceroute to dslreports.com (209.123.109.175), 30 hops max, 60 byte packets
1 ae7-3046.edge6.LosAngeles1.Level3.net (x.x.x.x) 6.190 ms 6.114 ms 6.063 ms
2 vlan80.csw3.LosAngeles1.Level3.net (4.69.144.190) 81.403 ms vlan60.csw1.LosAngeles1.Level3.net (4.69.144.62) 82.876 ms vlan70.csw2.LosAngeles1.Level3.net (4.69.144.126) 88.763 ms
3 ae-73-73.ebr3.LosAngeles1.Level3.net (4.69.137.37) 81.755 ms ae-93-93.ebr3.LosAngeles1.Level3.net (4.69.137.45) 82.144 ms ae-63-63.ebr3.LosAngeles1.Level3.net (4.69.137.33) 81.823 ms
4 ae-3-3.ebr1.SanJose1.Level3.net (4.69.132.9) 81.304 ms 81.518 ms 81.358 ms
5 ae-2-2.ebr2.NewYork1.Level3.net (4.69.135.186) 81.534 ms 81.897 ms 81.836 ms
6 ae-92-92.csw4.NewYork1.Level3.net (4.69.148.46) 88.774 ms ae-82-82.csw3.NewYork1.Level3.net (4.69.148.42) 81.499 ms ae-62-62.csw1.NewYork1.Level3.net (4.69.148.34) 81.399 ms
7 ae-2-70.edge8.NewYork1.Level3.net (4.69.155.79) 81.947 ms 81.606 ms ae-3-80.edge8.NewYork1.Level3.net (4.69.155.143) 81.657 ms
8 NETACCESS.edge8.NewYork1.Level3.net (4.31.30.38) 81.836 ms 81.547 ms 81.983 ms
9 0.e1-1.tbr2.ewr.nac.net (209.123.10.133) 81.934 ms 82.130 ms 0.e1-4.tbr2.mmu.nac.net (209.123.10.77) 82.813 ms
10 0.e1-4.tbr2.oct.nac.net (209.123.10.126) 83.052 ms 82.491 ms 0.e1-1.tbr2.oct.nac.net (209.123.10.21) 82.969 ms

Mele20
Premium
join:2001-06-05
Hilo, HI
kudos:5
reply to NormanS
Until recently, MIT traces showed MIT to be backbone (on backbone - their own) and the final hop was firewalled (unless you did a TCP trace). Yes, content is now stored on Akamai servers which is something quite new and thus surprised me. Besides, I'm sort of like Konaguy See Profile in that I will generally believe certain individuals here at Oceanic (those actually in a position to know which is not the average employee that most RR users would speak with) over folks posting in this forum.

There is NO added latency with going through San Jose now. You are wrong about that. It is still 137ms average to dslreports.com (after pinging now for 19.5 hours). I agree that the seeming anomaly of where the jump takes place in the ping time is likely due to a change in how the routers are named but I don't know that for sure although it is the most likely explanation.
--
When governments fear people, there is liberty. When the people fear the government, there is tyranny. Thomas Jefferson


NormanS
I gave her time to steal my mind away
Premium,MVM
join:2001-02-14
San Jose, CA
kudos:12
Reviews:
·SONIC.NET
·Pacific Bell - SBC
said by Mele20:

Until recently, MIT traces showed MIT to be backbone (on backbone - their own) ...

The question is, "How do you define a backbone?" If you mean they are their own transit provider, then every ISP is a backbone:
Tracing route to cookie.hupkid.us [173.228.19.254]
over a maximum of 30 hops:
 
  1     2 ms     9 ms     9 ms  Chihiro [192.168.102.1]
  2    37 ms    34 ms    33 ms  173-228-7-1.dsl.static.sonic.net [173.228.7.1]
  3    30 ms    39 ms    29 ms  gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
  4    37 ms    39 ms    39 ms  gig1-1-2.gw.snjsca12.sonic.net [70.36.243.22]
  5    68 ms    65 ms    62 ms  cookie.hupkid.us [173.228.19.254]
 
Trace complete.
 
How about that! My ISP is a backbone!

However, I suspect they have to pay for transit at some point; only "settlement free" Tier 1 transit networks don't pay for transit. Everybody else pays; at the least a Tier 1 transit network for transit.
Tracing route to www.google.com [74.125.239.116]
over a maximum of 30 hops:
 
  1     3 ms     5 ms     3 ms  Chihiro [192.168.102.1]
  2    26 ms    31 ms    39 ms  173-228-7-1.dsl.static.sonic.net [173.228.7.1]
  3    36 ms    29 ms    39 ms  gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
  4    36 ms    29 ms    39 ms  0.xe-5-1-0.gw.pao1.sonic.net [69.12.211.1]
  5    37 ms    38 ms    39 ms  0.xe-6-0-0.gw.equinix-sj.sonic.net [64.142.0.185]
  6    36 ms    29 ms    38 ms  eqixsj-google-gige.google.com [206.223.116.21]
  7    27 ms    38 ms    35 ms  216.239.49.170
  8    34 ms    28 ms    39 ms  66.249.95.29
  9    36 ms    38 ms    37 ms  nuq05s01-in-f20.1e100.net [74.125.239.116]
 
Trace complete.
 
Do you suppose the peering handoff from Sonic.net (my ISP) is "settlement free"? If one party pays another for transit, which is the "backbone"?

There is NO added latency with going through San Jose now. You are wrong about that. It is still 137ms average to dslreports.com (after pinging now for 19.5 hours). I agree that the seeming anomaly of where the jump takes place in the ping time is likely due to a change in how the routers are named but I don't know that for sure although it is the most likely explanation.

Linear distance (great circle) Hawaii to San Francisco, or Hawaii to Tustin is about the same. Linear distance (great circle) San Francisco to New Jersey, or Tustin to New Jersey is about the same. Jumping from Tustin to San Jose adds some distance; it is definitely not 0 ms latency between them.

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum

Mele20
Premium
join:2001-06-05
Hilo, HI
kudos:5
MIT is Tier 1 backbone. I could easily prove it but you are so combative that I don't feel like bothering to go fetch some of the hundreds of Ping Plotter's to MIT over many years and post a screen shot. Screenshots taken every hour automatically with Ping Plotter Pro don't always save correctly so I probably would have to load the sample set into Ping Plotter and then do a third party screenshot.

As for ping time to dslr via old or new routing, you keep insisting I am lying. I am not. Ping time is 137ms average whatever the routing - LA to Washington, DC, Newark, or LA to San Jose, New York. As to why that is, I already gave my best guess so I'm out of this discussion.
--
When governments fear people, there is liberty. When the people fear the government, there is tyranny. Thomas Jefferson

34764170

join:2007-09-06
Etobicoke, ON
said by Mele20:

MIT is Tier 1 backbone.

You have no idea what you're talking about.