said by myco :

from telus:

"Your traceroute results indicate that your computer begins to lack speed after your computer leaves the TELUS network. Unfortunatley, this is not something TELUS can troubleshoot as the problem exists outside of the TELUS network. I apologize on behalf of TELUS for the inconvenience this issue has caused you."

said by netwerk :

I'm still trying to get this resolved.

route-views.ab>show bgp paths 32751
Address Hash Refcount Metric Path
0x659A52A8 1250 2 0 852 2828 6993 32751 i
0x6423A460 1558 2 0 852 174 32751 i
0x6D9977C0 1621 2 0 852 174 3549 14744 32751 i
0x6D658A20 3040 2 0 852 1239 3356 25973 32751 32751 32751 32751 32751 32751 i

said by Randsl Dude :

Network peering is as complicated as the wiring on the space shuttle.

Telus would have signed a contract with all the large Isp network operators in the United States on how mutual network traffic would be handled, and by the way, Telus would be considered a small fry ISP in the U.S.

Within each large Isp's networks, say AT& T's for example, are hundreds of smaller network operators also seeking peering arrangements, ranging from free access to hundreds of thousands of dollars for access.

It's only fair that the larger Isp's are allowed to manage the traffic on their own networks from other networks like Telus's, to ensure a reliable flow of network traffic for the majority of the 'public" users.

Private peering companies like Duck Soup and Nuclear Fallout may have peering arrangements with public US ISP's or private ISP's like Cogent but not with Telus.

Your ping sky rockets when it hits the server at hop 4, wherever that one is, which hands off to the Cogent private peering network...»www.cogentco.com/us/network_map.php

...that's where the problem is because they don't have a cross border peering arrangement with any Canadian Isp in the West, just down east, most likely with Bell.

It's a routing problem alright and it resides with Cogent and whoever they have a peering agreement with, and it sure isn't Telus...