<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Qwest routing change recently? in Qwest</title>
<link>http://www.dslreports.com/forum/r17969859</link>
<description></description>
<language>en</language>
<pubDate>Wed, 02 Dec 2009 17:12:31 EDT</pubDate>
<lastBuildDate>Wed, 02 Dec 2009 17:12:31 EDT</lastBuildDate>

<item>
<title>Re: Qwest routing change recently?</title>
<link>http://www.dslreports.com/forum/remark,17998335</link>
<description><![CDATA[<A HREF="/useremail/u/1141361"><b>caffeinator</b></A> : Ah, interleave, I have, it's just my ISP also runs a regional datacenter...5 miles away. They are very well connected.<br><br>I'm guessing you ran that from CET, which would be cheating.<br><br>I can beat most any qwest trace. We have time warner backbones and others as well, more than CET. And, I'm damn near sitting on Mae West just like u. Google that.<br><br>We got more dark fiber here than most cities have lit, eh? Terabyte Triangle and such nonsense.<br><br>Gimme a target, i'll trace it. :)<br><br>Can I trace from my 56 Marietta account?.<br><br>I used yahoo as a baseline only.<br><br>I'm on 1.5 service, but I can get 7M..which blows our Comtastic buddies out of the water. For less since I don't have TV service.<br><br>I see yer from CET..fun..you guys still in business eh?<br>Funny how ya crash every so often...least ya don't do half the p0rn Icehouse does.<br><br>*boinkBoard*<br><br>-CaFF<br><SMALL>--<br>"Only two things are infinite, the universe and human stupidity, and I'm not sure about the former." - A. Einstein</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,17998335</guid>
<pubDate>Wed, 14 Mar 2007 04:05:58 EDT</pubDate>
</item>

<item>
<title>Re: Qwest routing change recently?</title>
<link>http://www.dslreports.com/forum/remark,17995187</link>
<description><![CDATA[<A HREF="/useremail/u/395330"><b>christcorp</b></A> : Ask Al Gore. That's how the internet is designed. There are many different entities involved in moving traffic around the world. An ISP could do direct routing, but then that would cost them a lot more money to have trunks to multiple places throughout the world. By centralizing the ISP in a few places, then shipping off to a backbone provider like Level 3, an ISP can be much more efficient and cost effective. The majority of most people's web connections aren't usually in their own town. Later... Mike...]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,17995187</guid>
<pubDate>Tue, 13 Mar 2007 16:01:07 EDT</pubDate>
</item>

<item>
<title>Re: Qwest routing change recently?</title>
<link>http://www.dslreports.com/forum/remark,17994768</link>
<description><![CDATA[<A HREF="/useremail/u/669545"><b>hurfy</b></A> : Umm, qwest does not have a problem going to California....EVERYTHING (from here) on Qwest seems to go to Califonia, even if i want to go next door :(<br><br>I resolve yahoo.com to a diferent number so i entered the IP you used. Qwest from Spokane. Looks like you would beat me by 10ms IF i was interleaved :)<br><br>Tracing route to w2.rc.vip.scd.yahoo.com [66.94.234.13]<br>over a maximum of 30 hops:<br><br>  1     1 ms     2 ms     1 ms  71.216.33.238<br>  2    22 ms    21 ms    22 ms  spkn-dsl-gw02-194.spkn.qwest.net [207.225.41.194]<br>  3    41 ms    22 ms    21 ms  spkn-agw1.inet.qwest.net [207.225.41.93]<br>  4    37 ms   122 ms    21 ms  spk-core-01.inet.qwest.net [205.171.153.33]<br>  5    29 ms    30 ms    29 ms  tuk-core-01.inet.qwest.net [205.171.5.54]<br>  6    46 ms    46 ms    46 ms  svl-core-01.inet.qwest.net [67.14.12.6]<br>  7    46 ms    46 ms    47 ms  pax-brdr-02.inet.qwest.net [205.171.214.38]<br>  8    47 ms    46 ms    47 ms  if-1-1.core3.PDI-PaloAlto.Teleglobe.net [207.45.213.133]<br>  9    46 ms    48 ms    48 ms  ix-6-2.core3.PDI-PaloAlto.Teleglobe.net [207.45.213.130]<br> 10    47 ms    48 ms    47 ms  ge-4-0-0-p450.msr2.scd.yahoo.com [216.115.106.205]<br> 11   206 ms    48 ms    57 ms  ten-1-3-bas2.scd.yahoo.com [66.218.82.219]<br> 12    48 ms    49 ms    48 ms  w2.rc.vip.scd.yahoo.com [66.94.234.13]<br><br>Trace complete.<br><br>I haven't checked if the routing on my home ISP is diferent. The ping to seattle was 20ms when i used their game servers long ago.<br><br>Someday i would love to know why it is best for the internet signal to go 3000 miles to talk to someone down the block....Seems the pipes would be cleaner if there wasn't a 3000 mile joyride.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,17994768</guid>
<pubDate>Tue, 13 Mar 2007 14:41:45 EDT</pubDate>
</item>

<item>
<title>Re: Qwest routing change recently?</title>
<link>http://www.dslreports.com/forum/remark,17985745</link>
<description><![CDATA[<A HREF="/useremail/u/159054"><b>brmasha</b></A> : lingotech, check out xmission, they are a local SLC ISP that peer with several backbone providers.  If you want me to run a traceroute for you just PM me and I would be happy to.<br><br>Check out &raquo;<A HREF="http://stats.xmission.com/routers/public" >stats.xmission.com/routers/public</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,17985745</guid>
<pubDate>Sun, 11 Mar 2007 22:16:36 EDT</pubDate>
</item>

<item>
<title>Re: Qwest routing change recently?</title>
<link>http://www.dslreports.com/forum/remark,17976501</link>
<description><![CDATA[<A HREF="/useremail/u/1141361"><b>caffeinator</b></A> : Agreed, I love my ISP's routing.<br><br>For example, tracert to yahoo (in cali) goes pretty much straight there from here in eastern WA. <br><br>Bam, from here to Oakland ...a nice hop there ;)<br><br>--- 03/10/07 00:00:36 Pacific Standard Time<br>--- looking up host yahoo.com<br>--- traceroute to yahoo.com [66.94.234.13],<br>    30 hops max, 18 byte packets<br><br>  1  [   66.45.176.66]  66-45-176-66.ptr.llix.net  30 ms  <br>  2  [   66.45.176.65]  66-45-176-65.ptr.llix.net  40 ms  <br>  3  [    65.61.96.49]  65.61.96.49  40 ms  <br>  4  [     65.61.96.9]  br1-ge-1-0.spkn.llix.net  30 ms  <br>  5  [  66.193.134.53]  66.193.134.53  120 ms  <br>  6  [ 66.192.248.164]  dist-01-ge-3-0-0-510.spkn.twtelecom.net  40 ms  <br>  7  [   66.192.250.0]  core-01-so-3-0-0-0.okld.twtelecom.net  71 ms  <br>  8  [  64.129.248.19]  peer-02-so-0-0-0-0.palo.twtelecom.net  70 ms  <br>  9  [ 66.192.252.112]  66.192.252.112  70 ms  <br> 10  [216.115.106.207]  ge-4-0-0-p451.msr2.scd.yahoo.com  60 ms  <br> 11  [  66.218.82.223]  ten-2-3-bas2.scd.yahoo.com  71 ms  <br> 12  [   66.94.234.13]  w2.rc.vip.scd.yahoo.com  70 ms  <br><br>--- traceroute statistics for yahoo.com<br>    12 packets transmitted, 12 received<br>    round-trip time (ms) min 30, avg 59, max 120<br><br>Not bad for my 1.5M service. <br><br>I do pay a bit more, but I feel it's worth it.<br><br>-CaFF<br><SMALL>--<br>"Only two things are infinite, the universe and human stupidity, and I'm not sure about the former." - A. Einstein</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,17976501</guid>
<pubDate>Sat, 10 Mar 2007 03:06:27 EDT</pubDate>
</item>

<item>
<title>Re: Qwest routing change recently?</title>
<link>http://www.dslreports.com/forum/remark,17975475</link>
<description><![CDATA[<A HREF="/useremail/u/395330"><b>christcorp</b></A> : You are absolutely correct. That is the one major thing going for Qwest DSL. You can use a 3rd party ISP. As such, your physical Qwest DSL routes via a proxy; (3rd party ISP). If you find the right one, you can indeed have some better traceroutes to where you might want to go. The key of course if finding a 3rd party ISP that has a direct connection to Qwest in your town and has good contract backbones to the internet. It won't ever be as long a latency as cable, but it will be possibly less than the Qwest.net/Qwest MSN dsl tracing to the same sights. Of course, the best thing to do is to visit one of these 3rd party ISP's in your town and have them let you do all the trace routes you want to see if you are happy.<br><br>For a list of all the 3rd party providers, just go to qwest.net at the bottom is "High Speed Internet". Then on the left is "Other ISPs". Then click on your state. Then on the left is "ISP LIST". It will list ALL 3rd party DSL ISP's that have a connection agreement with Qwest in your state. Then just go to some of the ones you like; possibly in the same town; and see if you like their connections. Later... Mike...]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,17975475</guid>
<pubDate>Fri, 09 Mar 2007 21:43:31 EDT</pubDate>
</item>

<item>
<title>Re: Qwest routing change recently?</title>
<link>http://www.dslreports.com/forum/remark,17973955</link>
<description><![CDATA[<A HREF="/useremail/u/621958"><b>AthlGrond</b></A> : Mike I think he was experiencing some new routing latency rather than just the usual interleave variety.<br><br>And I think DSL can be consistently better for routing if you choose an ISP that has multiple backbone connections. (They're out there, you just have to look for them.)<br><br>Unfortunately I can't comment on Qwest routing issues from personal experience since we aren't using them for our ISP here at the office.<br><SMALL>--<br>"Talk about the goats guarding the garbage!" -Dick Morris</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,17973955</guid>
<pubDate>Fri, 09 Mar 2007 17:09:40 EDT</pubDate>
</item>

<item>
<title>Re: Qwest routing change recently?</title>
<link>http://www.dslreports.com/forum/remark,17972943</link>
<description><![CDATA[<A HREF="/useremail/u/395330"><b>christcorp</b></A> : As you can see, there aren't a lot of responses. That's because it's generally accepted, that if you are that picky about latency and are an avid gamer who wants the fastest, that you should go with cable and not Qwest DSL. Qwest DSL using interleaving which adds an additional 32ms to all round trip pings. You aren't going to get away from that. At least not for a while. Not until Qwest changes that. <br><br>Most people prefer the stability and lack of jitter with Qwest dsl over cable. Cable may have lower latency, but that latency and bandwidth isn't as consistent as Qwest DSL is. Almost all of my traceroutes go through Dallas. Qwest does a lot of hand off to Level 3. That's where one of their biggest connection points are. I am in Wyoming, and a trace to california will still go to Denver, then Dallas, then to California. That's the way it is. Later... Mike....]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,17972943</guid>
<pubDate>Fri, 09 Mar 2007 14:38:37 EDT</pubDate>
</item>

<item>
<title>Qwest routing change recently?</title>
<link>http://www.dslreports.com/forum/remark,17969859</link>
<description><![CDATA[<A HREF="/useremail/u/945143"><b>lingotech</b></A> : Hello.<br><br>Just out of salt lake city and have had quest dsl for a bit now. My concern came up because untill yesterday i had decent ping times from 50-70 coming from salt lake to california. But all of a sudden my ping time increased to 100+. I checked my modem, upgraded the firmware on it and nothing. So i went to my neighbors who have the same connection and had the same problem.<br><br>I then decided to dig a little further and do a tracert the gaming servers i usually play at.<br><br>i noticed on the 4th hop it is skipping over to dallas when  it used to not... and from out of dallas i start to get worse ping.<br><br>Anyone else noticing a new lag comming from qwest?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,17969859</guid>
<pubDate>Thu, 08 Mar 2007 22:55:39 EDT</pubDate>
</item>

</channel>
</rss>
