dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
2729
share rss forum feed


pfak
Premium
join:2002-12-29
Vancouver, BC
reply to firstness

Re: [AB] Telus routing Edmonton-Seattle traffic through Chicago

Severe packet loss between Telia and TELUS in Seattle. Ugh!
--
The more I C, the less I see.

WhosTheBosch

join:2009-12-02
reply to firstness
A lot of Telus' peering issues could be solved by joining SIX in Seattle, however, for whatever corporate reason they're against it. Shaw, SaskTel, Novus, Primus and Bell are all a member which is why they have a large number of better routes through the West coast. If Telus got involved with SIX they would have direct peers with a large number of companies:

»www.seattleix.net/participants.htm

Facebook
Akami
AT&T
Bell
Shaw
Limelight
Netflix
OpenDNS
nLayer
Microsoft
Peer1
Softlayer
Yahoo

Most of these companies handle a large amount of the Internets bandwidth or host companies that do, so by not peering within SIX Telus is causing bad routing issues within it's network on the west coast.

Also, the OP's problems would be solved as WowRack is also a member of SIX.

WhosTheBosch

join:2009-12-02
reply to rustydusty
said by rustydusty:

Umm, nlayer and Internap are high end backbone providers, not low at all. If anything, XO is the cheaper end of any of them. I've had awesome luck with Internap.

They may be high VOLUME backbone providers, however they are not high QUALITY bandwidth providers.


rustydusty

join:2009-09-29
Red Deer, AB

1 edit
reply to firstness
Time and time again, I get more consistent routes and pings to any Internap provider. Even better because they have such a mix and their FCP is beautiful. Never seen such consistency between multiple locations in the US. They are more expensive for a reason.

»as.robtex.com/as14745.html#graph


pfak
Premium
join:2002-12-29
Vancouver, BC
I like Internap! But of course TELUS fowls it up by going via Cogent :)

traceroute to crash.pfak.org (204.14.120.68), 30 hops max, 40 byte packets using UDP
 1  10.31.198.1 (10.31.198.1)  8.114 ms   6.963 ms   6.363 ms
 2  204.225.243.22 (204.225.243.22)  10.919 ms   10.751 ms   10.765 ms
 3  te7-4.ccr02.sea02.atlas.cogentco.com (154.54.10.45)  10.270 ms   10.170 ms   13.844 ms
 4  te2-7.ccr02.sea01.atlas.cogentco.com (154.54.85.181)  10.171 ms te2-8.ccr02.sea01.atlas.cogentco.com (154.54.85.185)  30.183 ms te2-7.ccr02.sea01.atlas.cogentco.com (154.54.85.181)  9.191 ms
 5  te4-2.ccr01.sea03.atlas.cogentco.com (154.54.41.146)  34.785 ms   33.464 ms   32.482 ms
 6  Internap-Network-Services.demarc.cogentco.com (38.104.124.82)  10.281 ms   13.763 ms   13.879 ms
 7  border2.te12-1-bbnet1.sea.pnap.net (63.251.160.7)  12.962 ms border2-bbnet2.sea.pnap.net (63.251.160.78)  10.986 ms border2.te12-1-bbnet1.sea.pnap.net (63.251.160.7)  10.657 ms
 8  farreachnet-2.border2.sea.pnap.net (206.253.223.190)  10.846 ms   9.963 ms   9.570 ms
 9  216.18.239.26 (216.18.239.26)  11.738 ms   11.537 ms   10.906 ms
10  gw.pfak.org (204.14.120.66)  9.755 ms   11.311 ms   9.712 ms
11  crash.pfak.org (204.14.120.68)  10.133 ms   9.533 ms   9.331 ms
 

--
The more I C, the less I see.

jwvo

join:2001-07-27
Seattle, WA
We (spectrumnet.us) just turned up peering with telus in Seattle. This issue should be fixed now.