A global ISP tracker called “The Network is Aware” shows the processed data of a test used to detect whether an ISP is throttling downloads that use a particular protocol.
According to the website, which is hosted at Syracuse University and overseen by Professor Milton Mueller and his team, the project specifically seeks to detect deep packet inspection (DPI).
“Thanks to an initiative known as the Measurement Lab (MLab), supported by Google, the New America Foundation and the PlanetLab Consortium, the Glasnost test allows end users all over the world to test whether their ISP is blocking or throttling BitTorrent and other protocols,” states The Network is Aware website.
“The results are stored and made available to researchers.”
The website allows you to filter results by country, and South Africa is among the countries listed.
|Operator Name||Quarter||Number Of Valid Tests||% of Tests Showing DPI|
|Telkom South Africa||2009Q1||16||13%|
|Telkom South Africa||2009Q2||29||28%|
|Telkom South Africa||2009Q4||19||21%|
|Telkom South Africa||2010Q1||28||11%|
However, one hopes that more users might start using the test so that over time the list will become more comprehensive.
Most of the time the Glasnost test warned us that “the measurement data is too noisy to detect whether your ISP rate limits your download traffic.” This was despite attempts to minimise the amount of Internet traffic generated on the network.
The test with which we had the most success was the Telkom HTTP benchmark, which ran on ports 38929 and 44023.
|Telkom: All HTTP and control flow transfers using port 38929|
|Transfer direction||Bandwidth HTTP flow||Bandwidth control flow|
|Download #1||2,237 kbps||2250 kbps|
|Download #2||2,237 kbps||1468 kbps|
|Download #3||1,757 kbps||1781 kbps|
|Upload #1||307 kbps||400 kbps|
|Upload #=2||401 kbps||400 kbps|
|Upload #3||402 kbps||396 kbps|
According to Glasnost, there were no indications that Telkom limits HTTP downloads, though the maximum speed achieved was 2,250kbps.
Looking across all our tests, the best speeds we achieved were between 2,048kbps (2Mbps) and 2,697kbps. If that is considered the “expected speed” for the purposes of this exercise, then our tests yielded the following results:
- MWeb shaped torrent downloads heavily during the day, but not uploads.
- Telkom’s (far more expensive) uncapped account did not seem to shape BitTorrent downloads.
- WebAfrica also shaped BitTorrent downloads into the ground, showing speeds slower than that achieved on upload tests.
- Uploads usually ran at around 400kbps, close to what is expected from the type of ADSL connection we tested on.
- The accounts performed similarly on HTTP download tests.
Since tests take around 8 minutes each to run and need you to keep your connection as quiet as possible, the performance of NNTP and Flash video on various connection was left for a future exercise.
|MWeb: BitTorrent transfers using port 6881 and 58791|
|Transfer direction||Bandwidth BitTorrent flow||Bandwidth control flow|
|Download #1||68 kbps||1179 kbps|
|Download #2||432 kbps||293 kbps|
|Download #3||1,055 kbps||90 kbps|
|Upload #1||382 kbps||402 kbps|
|Upload #=2||403 kbps||399 kbps|
|Upload #3||402 kbps||406 kbps|