Diji1, Exetel senior people have already posted that neither they nor AAPT are filtering torrent connections. Something has changed, and was widely publicised; namely the cache removal, that as a by-product can disguise some torrent problems.
My torrent result is above, done at home on Sunday afternoon immediately after your post came in. Let's keep testing restricted to the major software "public" torrents (Mint, Ubuntu, LibreOffice etc), because we can usually guarantee no difficulties with swarms or people trying to hide their behaviour. The only way I have been able to get terrible results on the major "public" software torrents has been to deliberately interfere with my router and ruin the torrent client configurations. I don't even have to fully optimise my system to get 800+ kB/s. My conclusion has been that people who are slow on these particular downloads probably need to attend to their computers.
I wouldn't run to conspiracy theories as I have read without doing some serious looking of my own. All the software for creating torrent packets, fancy route tracing, router and NIC monitoring, etc, is available on specialist Linux distros if you want to try them. But if I can max my line, why waste time looking elsewhere? More worthwhile would be checking for transient local exchange congestion.
I apologise for getting technical, but so is torrenting:
Have you ever checked the behaviour of your router under huge numbers of connections? (conntrack, TTL, etc). It's a normal computer, and if it is reasonably recent, you really won't need to if you tightly control connections at the client. Have you monitored the traffic through your computer? Most important, think about the choking algorithm and how you handle it (see http://www.bittorrent.org/beps/bep_0003.html
). Note the last half page, starting "Choking is done for several reasons". Eittenberger et al, 2011, put it this way:
The peer selection strategy is handled by the so called choking algorithm. To encourage peers to contribute their resources for the data dissemination, a tit-for-tat mechanism is implemented to impede free-riding, i.e. peers not contributing data to the network should not be able to achieve high download rates. Instead, this choking algorithm provides sharing incentives by rewarding peers who contribute data to the system. The algorithm determines the selection of peers to exchange data with. Peers that upload data at high rates are preferred. Once per choking period, usually every ten seconds, a peer evaluates the transmission rates from all the connected peers and selects a fixed number of the fastest ones, depending on its upload capacity. It will only upload data to these unchoked peers in this period. from other peers are denied in this period, i.e. those peers are choked. Another important part of the algorithm is the optimistic unchoking behavior: every 30 seconds one peer is randomly chosen and will be unchoked. This is meant to explore new peers with even higher upload capacities an as a side effect ensures data dissemination to low-capacity peers. Once a leecher has finished the download and enters the seeding state, it follows a different unchoke strategy. In most of the implementations peers in seed state unchoke peers with the highest download capacity to optimize the general dissemination performance of the network and to maintain high upload utilization.
Next consider the number of connections you open. TCP control does not behave optimally with excessive connections, which stress routers, and particularly wireless transmitters. For the least problems here, and to optimise the torrent algorithm, limit upload slots based on upload speed to make sure that each connected peer is getting a reasonable amount of bandwidth.
Some clients do a better default config than others - I have recommended Deluge previously for this reason. It has a comprehensive config GUI, which is easier than tracking down resource files.