| Author | Message | ||
     Mike Skovgaard (Meatheadmike) Member Username: Meatheadmike Post Number: 1 Registered: 11-2007 |
Well, if this is the place to discuss network neutrality, I can definitely attest to the actions of my ISP. It appears that they are doing 2 different things that affect my internet usage. a) They are blocking port 25 SMTP except for mail relayed though shaw's server at shawmail.vc.shawcable.net. I understand why they are doing this, it is supposedly a spam management technique. But the grief that it causes end users if immeasurable. For instance most of the staff at my company has laptops which are configured to work with our company's SMTP. When they go home, they cant send mail. If they set up the SMTP to go through Shaw, then they can't send mail when they are at the office. So everyone now needs to have two email accounts configured in order access their single mailbox  Yes, I know that we could simply port forward 25 to somewhere else, but that's not the point. b) Bit torrent traffic is being severely throttled. It appears to be a Shaw thing. I base this on an observation over the past few months. I'm signed up for Shaw's "Xtreme-I" service which supposely gives me a 10Mb downlink bandwidth: http://www.shaw.ca/en-ca/ProductsServices/Internet/Xtreme-I/. When I download files via FTP or sFTP, my files transfer nice and fast (although nowhere near 10Mbps mind you). In fact a speed test that I just ran here pegs me at 5Mbps. But if I download torrents, even ones that have *thousands* of seeds, I never get more than 300Kbs. In fact even when I'm pegged at 300Kbps, loading a second or third torrent always results in a shared bandwidth never exceeding 300Kbps. It seems a bit suspicious to me, since it's all very consistent as of late. | ||
| (Unregistered Guest) Unregistered Guest |
Greetings, Any issues that you are having must be either shawcable network related (check in a traceroute) or the end server related (that you can also see in a trace, or in repeated pings). Doing a trace out from SEA2 to your IP it's fine, traceroute to 70.75.79.21 (70.75.79.21), 64 hops max, 40 byte packets 1 vl102-d2.acc.sea2.hopone.net (209.160.40.3) 0.294 ms 0.242 ms 0.238 ms 2 ge5-2.core1.sea2.hopone.net (209.160.60.242) 0.223 ms 0.148 ms 0.148 ms 3 ge5-0.core1.sea1.hopone.net (66.36.224.22) 0.404 ms 0.440 ms 0.458 ms 4 rc1wt-ge4-1.wa.shawcable.net (198.32.180.54) 0.615 ms 0.472 ms 0.504 ms 5 rc2wh-pos0-0-5-0.vc.shawcable.net (66.163.76.153) 26.223 ms 26.626 ms 25.810 ms 6 rc1so-pos11-0.cg.shawcable.net (66.163.76.9) 38.945 ms 39.471 ms 39.114 ms 7 rd1so-ge6-0.cg.shawcable.net (66.163.71.130) 39.227 ms 40.167 ms 40.579 ms 8 dx2ru-g1.cg.shawcable.net (64.59.139.25) 40.093 ms 40.203 ms 39.236 ms 9 * * * however, the latency is a bit high as 40ms to Calgary - the issue seems to be the 26ms added from Seattle to go to Vancouver, that should be normally only some 2-4ms. So, it seems that Shawcable is having some issues on their network between Vancouver and Seattle. If you are concerned about that, you may want to contact them. However, there is nothing we can do about that, as we do not control third party networks such as Shawcable; only they can answer regarding the high latency that their network is giving in this route from Calgary to Seattle. As you can see, our network from the data centre (SEA2) to Shawcable interconnect at SEA1 is only 0.5 ms: 1 vl102-d2.acc.sea2.hopone.net (209.160.40.3) 0.294 ms 0.242 ms 0.238 ms 2 ge5-2.core1.sea2.hopone.net (209.160.60.242) 0.223 ms 0.148 ms 0.148 ms 3 ge5-0.core1.sea1.hopone.net (66.36.224.22) 0.404 ms 0.440 ms 0.458 ms 4 rc1wt-ge4-1.wa.shawcable.net (198.32.180.54) 0.615 ms 0.472 ms 0.504 mswhich is normal and how it always is. From that point, it's the Shawcable network. I hope this helps.. |