Over the past number of years when I looked at various connections, they did seem very odd and I wonder why they traverse into the states. I, too, would have thought connectivity would have improved ...<div><br></div><div>
I did a quick check (and it didn't take long to find an example) ... </div><div><br></div><div>I'm on <a href="http://les.net">les.net</a> and my traceroute to our neighbour to the west (Saskatchewan - city of Regina actually) takes me as such:<div>
<br></div><div>Les -> GT WPG -> GT VANCOUVER -> GT SEATTLE -> HE SEATTLE -> HE VANCOUVER -> SASKTEL ... </div><div><br></div><div>that's quite a few hops (and to the south) to go a few hundred km's to the west </div>
<div><br></div><div>Compare that to a Saskatoon connection ... </div><div><br></div><div>Les -> GT -> SHAW WPG -> BIGPIPE SASKATOON </div><div>(nice and light) ...</div><div><br></div><div>Some peer well, others don't ... room for growth and expansion I'd say :-)</div>
<div><br></div><div>Dan.</div><div><br><br><div class="gmail_quote">On Fri, Jun 29, 2012 at 2:16 PM, John Lange <span dir="ltr"><<a href="mailto:john@johnlange.ca" target="_blank">john@johnlange.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">... And I'd be very surprised if any Canada-to-Canada inter-ISP routing goes through the U.S so the "within Canada" statement doesn't seem a likely motivation either.<br>
<br>Don't get me wrong, I not anti IXP, I just don't see a need or a business case for it.<span class="HOEnZb"><font color="#888888"><br><br>John<br>
</font></span></blockquote></div><br></div></div>