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

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

<channel>
<title>Re: What the heck is up with telus routing????? in Telus</title>
<link>http://www.dslreports.com/forum/r20705494</link>
<description></description>
<language>en</language>
<pubDate>Wed, 11 Nov 2009 05:50:10 EDT</pubDate>
<lastBuildDate>Wed, 11 Nov 2009 05:50:10 EDT</lastBuildDate>

<item>
<title>Re: What the heck is up with telus routing?????</title>
<link>http://www.dslreports.com/forum/remark,20705494</link>
<description><![CDATA[<A HREF="/useremail/u/790826"><b>LazMan</b></A> : Kodak may not be a great example - they are hosted by Akamai, which does all kinds of load balanacing and availablility 'stuff' - the closest cluster or clusters to you may have been offline...<br><br>As for the routing - TELUS hands you to Cogent on the west coast - everyting from that part on (going to Boston, then DC, then NYC on AT&T) is outside TELUS's control...<br><br>Not to say the routing's alwasy RIGHT - just that it's not always thier fault, either...<br><br>Laz]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20705494</guid>
<pubDate>Thu, 26 Jun 2008 22:53:11 EDT</pubDate>
</item>

<item>
<title>Re: What the heck is up with telus routing?????</title>
<link>http://www.dslreports.com/forum/remark,20702318</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : If you look at the Telus and Shaw national network they both have backhaul routes through the US using some sort of peering agreement they must have the the Telco's down there.  I think it's probably cheaper for them to use those routes.  I know all my US bound traffic goes through Seattle from here in BC. The only time it goes through Toronto is if I'm accessing something in Ontario, Quebec.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20702318</guid>
<pubDate>Thu, 26 Jun 2008 12:15:08 EDT</pubDate>
</item>

<item>
<title>Re: What the heck is up with telus routing?????</title>
<link>http://www.dslreports.com/forum/remark,20700041</link>
<description><![CDATA[<A HREF="/useremail/u/1167536"><b>FPoultice</b></A> :   <br> ;)  Be glad you aren't in Alberta right now:<br><br><b><small>Tracing route to kodak.com [63.240.119.110]<br>over a maximum of 30 hops:<br><br>  1    1 ms     1 ms     1 ms  home [192.168.1.254]<br>  2    45 ms    43 ms    45 ms  d205-206-**-*.abhsia.telus.net [205.206.**.*]<br>  3    45 ms    43 ms    43 ms  154.11.197.65<br>  4    77 ms    78 ms    76 ms  chcgildtgr00.bb.telus.com [154.11.11.34]<br>  5    78 ms    76 ms    76 ms  po5-0.core01.ord03.atlas.cogentco.com [154.54.10.237]<br>  6    78 ms    78 ms    76 ms  te4-1.ccr02.ord03.atlas.cogentco.com [154.54.3.246]<br>  7    76 ms    74 ms    76 ms  te9-1.ccr02.ord01.atlas.cogentco.com [154.54.25.69]<br>  8    97 ms    96 ms    98 ms  te2-1.ccr02.bos01.atlas.cogentco.com [154.54.7.170]<br>  9   108 ms   102 ms   102 ms  te2-3.ccr02.dca01.atlas.cogentco.com [154.54.6.138]<br> 10   132 ms   126 ms   110 ms  te4-1.mpd01.dca02.atlas.cogentco.com [154.54.2.182]<br> 11     *      102 ms   114 ms  vl3497.mpd01.iad01.atlas.cogentco.com [154.54.5.66]<br> 12   462 ms   472 ms   447 ms  192.205.35.105<br> 13   113 ms   118 ms   128 ms  tbr2.wswdc.ip.att.net [12.123.8.190]<br> 14   110 ms   112 ms   110 ms  cr2.wswdc.ip.att.net [12.122.16.117]<br> 15   110 ms   110 ms   108 ms  cr2.n54ny.ip.att.net [12.122.3.37]<br> 16   112 ms   110 ms   120 ms  tbr2.n54ny.ip.att.net [12.122.16.198]<br> 17   148 ms   185 ms   216 ms  gar13.n54ny.ip.att.net [12.123.0.53]<br> 18   548 ms     *      116 ms  mdf1-gsr12-2-pos-7-0.nyc3.attens.net [12.122.255.162]<br> 19   112 ms   112 ms   110 ms  mdf2-bi8k-2-gig1-1.nyc3.attens.net [63.240.64.16<br>6]<br> 20     *        *        *     Request timed out.<br> 21     *        *        *     Request timed out.<br> 22     *        *        *     Request timed out.<br> 23     *        *        *     Request timed out.<br> 24     *        *        *     Request timed out.<br> 25     *        *        *     Request timed out.<br> 26     *        *        *     Request timed out.<br> 27     *        *        *     Request timed out.<br> 28     *        *        *     Request timed out.<br> 29     *        *        *     Request timed out.<br> 30     *        *        *     Request timed out.<br><br>Trace complete.</small></b> :huh:<br><br>I may be having other issues as well, though.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20700041</guid>
<pubDate>Wed, 25 Jun 2008 22:32:38 EDT</pubDate>
</item>

<item>
<title>Re: What the heck is up with telus routing?????</title>
<link>http://www.dslreports.com/forum/remark,20698683</link>
<description><![CDATA[<A HREF="/useremail/u/998508"><b>Tikker_LoS</b></A> : it's ridiculously cheap to backhaul to toronto<br><br>I think everyone in canada passes thru toronto at some point]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20698683</guid>
<pubDate>Wed, 25 Jun 2008 17:46:44 EDT</pubDate>
</item>

<item>
<title>Re: What the heck is up with telus routing?????</title>
<link>http://www.dslreports.com/forum/remark,20693915</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Could be one of their main peering routes are down?  That's what the internet does, find ways around it until it get's fixed.  It obviously has not always been this way.  I'll bet this will resolve itself eventually.  Maybe a bad routing table somewhere or a router gone down.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20693915</guid>
<pubDate>Tue, 24 Jun 2008 20:59:44 EDT</pubDate>
</item>

<item>
<title>Re: What the heck is up with telus routing?????</title>
<link>http://www.dslreports.com/forum/remark,20689698</link>
<description><![CDATA[<A HREF="/useremail/u/1095344"><b>siberx4</b></A> : Yowzers, that's a nasty route. Just tried it myself (I'm in vancouver as well) and I'm getting the same one you are. 21 hops may actually be the longest route I've ever seen myself on my own connection. Telus obviously got a good deal on *that* peering agreement ;)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20689698</guid>
<pubDate>Tue, 24 Jun 2008 03:45:16 EDT</pubDate>
</item>

<item>
<title>What the heck is up with telus routing?????</title>
<link>http://www.dslreports.com/forum/remark,20689339</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I have been wondering why my web browser has been really slow lately... after some troubleshooting it looks like just about everything gets sent to Ontario or some hell out of way  city just to use cogentco<br><br>I usually use kodak.com as a benchmark. It used to be 8 hops from vancouver<br><br>Its now over 21<br><br> 1  192.168.1.1 (192.168.1.1)  0.741 ms  0.408 ms  0.339 ms<br> 2  wtf.wtf.wtf.wtf.bchsia.telus.net (wtf.wtf.wtf.wtf)  15.287 ms  15.251 ms  14.978 ms<br> 3  secure.ca.inter.net (154.11.89.130)  16.970 ms  17.442 ms  16.874 ms<br> 4  154.11.10.70 (154.11.10.70)  38.277 ms  38.651 ms  38.782 ms<br> 5  154.11.2.54 (154.11.2.54)  39.065 ms  38.719 ms  38.842 ms<br> 6  po9-0.core01.sfo01.atlas.cogentco.com (66.28.4.229)  39.742 ms  39.401 ms  39.797 ms<br> 7  te3-1.mpd01.sfo01.atlas.cogentco.com (154.54.3.102)  243.901 ms  39.434 ms  39.811 ms<br> 8  te4-1.mpd01.mci01.atlas.cogentco.com (154.54.6.33)  169.872 ms  109.350 ms  82.015 ms<br> 9  * * *<br>10  te3-3.mpd01.bos01.atlas.cogentco.com (154.54.7.82)  96.911 ms  96.439 ms  97.026 ms<br>11  te3-3.mpd01.dca01.atlas.cogentco.com (154.54.1.106)  101.989 ms *  102.298 ms<br>12  te8-1.mpd01.dca02.atlas.cogentco.com (154.54.1.70)  102.792 ms  103.331 ms te8-3.mpd01.dca02.atlas.cogentco.com (154.54.6.198)  102.843 ms<br>13  vl3495.mpd01.iad01.atlas.cogentco.com (154.54.5.62)  103.215 ms vl3496.mpd01.iad01.atlas.cogentco.com (154.54.5.46)  103.606 ms vl3494.mpd01.iad01.atlas.cogentco.com (154.54.5.42)  118.355 ms<br>14  192.205.35.105 (192.205.35.105)  286.326 ms  187.717 ms  299.695 ms<br>15  tbr2.wswdc.ip.att.net (12.123.8.190)  110.991 ms  111.328 ms  110.730 ms<br>16  cr2.wswdc.ip.att.net (12.122.16.125)  110.992 ms  110.304 ms  110.114 ms<br>17  cr2.n54ny.ip.att.net (12.122.3.37)  109.703 ms  110.266 ms  109.985 ms<br>18  tbr1.n54ny.ip.att.net (12.122.16.158)  110.815 ms  111.212 ms  112.066 ms<br>19  12.122.81.245 (12.122.81.245)  108.686 ms  109.674 ms  109.735 ms<br>20  mdf1-gsr12-2-pos-6-0.nyc3.attens.net (12.122.255.130)  109.737 ms  110.215 ms  109.760 ms<br>21  mdf2-bi8k-1-eth-2-3.nyc3.attens.net (63.240.66.30)  109.889 ms  109.405 ms  108.757 ms]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20689339</guid>
<pubDate>Tue, 24 Jun 2008 00:40:24 EDT</pubDate>
</item>

</channel>
</rss>
