Thread: Testing Lab for Home Broadband Users

Google and two other companies have create a suite of tools to test if your broadband service is truly giving you what you need. There is also a test where it tests if your BB provider is restricting torrent bandwidth. Here's a brief from the main article.

Google Inc. and two nonprofit partners Wednesday launched a Web site that lets consumers test their Internet connections to reveal possible interference and traffic management by service providers.

The site, Measurement Lab, addresses a need among academics who want to gather data on how Internet connections work in practice. While the workings of the core Internet "highways" are well known and standardized, it's difficult to find out what happens on the network of an Internet service provider, between the "highway" and the customer's home.

Here is the link to the testing page.

Thanks for the info. Tried running the Network Diagonistic Test using the tool but all the servers are offline.

Originally Posted by cool_techie_tvm

Thanks for the info. Tried running the Network Diagonistic Test using the tool but all the servers are offline.

The NPAD test is online, I am running it right now. Here's the link to the test page.

both the test links u provided are not working ...

yeah ! they r not working....

Sorry about that . Those site's must be dealing very heavy load, that might be one of the reason why you are getting a time out. A message from their site

We are sorry. Our measurement servers are currently busy. Please try again later.

Try these

Server 1
Server 2
Server 3


Static Servers


Some common stats can be found using this page.

Originally Posted by vikramjb

Sorry about that . Those site's must be dealing very heavy load, that might be one of the reason why you are getting a time out. A message from their site



Try these

Server 1
Server 2
Server 3


Static Servers


Some common stats can be found using this page.

i finally got one of those links to work for me .. but after starting the test ... ... cant wait for so long ... will try it later ... seems to be on heavy demand

local: Start Test
local: Control channel to server established.
local: version handshake complete.
remote: Waiting for test to start. Currently there are 48 tests ahead of yours.

Originally Posted by saurav_kataruka

i finally got one of those links to work for me .. but after starting the test ... ... cant wait for so long ... will try it later ... seems to be on heavy demand

Yeap, when i started one of those, I was like waiting behind a 100 or 110. When my turn did come, it said it's not able to access some port and went kaput :49:

Originally Posted by vikramjb

Yeap, when i started one of those, I was like waiting behind a 100 or 110. When my turn did come, it said it's not able to access some port and went kaput :49:

Had the same experience. After making me wait for 45 minutes the test just blanked out

Originally Posted by cool_techie_tvm

Had the same experience. After making me wait for 45 minutes the test just blanked out

Either we need to try in some obscure timing's when server will be free or wait a month or two till the news dies down and then we can test our BB at our sweet time

i still cant get lucky with this.. ...

Originally Posted by saurav_kataruka

i still cant get lucky with this.. ...

Anybody is having any luck with the links ?

Originally Posted by vikramjb

Anybody is having any luck with the links ?

i cannot figure out whats wrong with this site ... this is the result of another 30 min wait ...

local: Start Test
local: Control channel to server established.
local: version handshake complete.
remote: Waiting for test to start. Currently there are 1 tests ahead of yours.
remote: Waiting for test to start. Currently there are 1 tests ahead of yours.
remote: Waiting for test to start. Currently there are 1 tests ahead of yours.
remote: Waiting for test to start. Currently there are 1 tests ahead of yours.
remote: Waiting for test to start. Currently there are 1 tests ahead of yours.
remote: Waiting for test to start. Currently there are 1 tests ahead of yours.
remote: Waiting for test to start. Currently there are 1 tests ahead of yours.
remote: Waiting for test to start. Currently there are 1 tests ahead of yours.
remote: Waiting for test to start. Currently there are 1 tests ahead of yours.
remote: Waiting for test to start. Currently there are 1 tests ahead of yours.
remote: Waiting for test to start. Currently there are 1 tests ahead of yours.
remote: Waiting for test to start. Currently there are 1 tests ahead of yours.

Originally Posted by saurav_kataruka

i cannot figure out whats wrong with this site ... this is the result of another 30 min wait ...

Bit torrent throttling simple test is working here. Let me if it works for you guys, I am off to try the advanced test.

Just finished the Full Test, not much difference with simple test. Neverthless It ran and gave me information on three specific ports. Here's the result of the full test.

Is BitTorrent traffic on a well-known BitTorrent port (6881) throttled?

* The BitTorrent upload (seeding) worked. Our tool was successful in uploading data using the BitTorrent protocol.

* There's no indication that your ISP rate limits your BitTorrent uploads. In our tests a TCP upload achieved minimal 202 Kbps while a BitTorrent upload achieved maximal 214 Kbps. You can find details here.

* The BitTorrent download worked. Our tool was successful in downloading data using the BitTorrent protocol.

* There's no indication that your ISP rate limits your BitTorrent downloads. In our tests a TCP download achieved minimal 72 Kbps while a BitTorrent download achieved maximal 111 Kbps. You can find details here.


Is BitTorrent traffic on a non-standard BitTorrent port (10009) throttled?

* The BitTorrent upload (seeding) worked. Our tool was successful in uploading data using the BitTorrent protocol.

* There's no indication that your ISP rate limits your BitTorrent uploads. In our tests a TCP download achieved minimal 182 Kbps while a BitTorrent download achieved maximal 181 Kbps. You can find details here.

* The BitTorrent download worked. Our tool was successful in downloading data using the BitTorrent protocol.

* There's no indication that your ISP rate limits your BitTorrent downloads. In our tests a TCP download achieved minimal 95 Kbps while a BitTorrent download achieved maximal 97 Kbps. You can find details here.


Is TCP traffic on a well-known BitTorrent port (6881) throttled?

* There's no indication that your ISP rate limits all downloads at port 6881. In our test, a TCP download on a BitTorrent port achieved at least 72 Kbps while a TCP download on a non-BitTorrent port achieved at least 95 Kbps. You can find details here.

* There's no indication that your ISP rate limits all uploads at port 6881. In our test, a TCP upload on a BitTorrent port achieved at least 202 Kbps while a TCP upload on a non-BitTorrent port achieved at least 182 Kbps. You can find details here.

Unfortunately the NPAD test is not working and this is the message I am getting

local: Start Test
local: Control channel to server established.
local: version handshake complete.
remote: Waiting for test to start. Currently there are 2 tests ahead of yours.
remote: Waiting for test to start. Currently there are 2 tests ahead of yours.
remote: Waiting for test to start. Currently there are 2 tests ahead of yours.
remote: Waiting for test to start. Currently there are 1 tests ahead of yours.
remote: Waiting for test to start. Currently there are 1 tests ahead of yours.
remote: Waiting for test to start. Currently there are 1 tests ahead of yours.
local: discard thread: listening for discard data on port 8003...
remote: It seems as though the data connection is not really running (Zero RTT)
remote: error: Pathdiag failed to generate report.
local: discard thread: stopped listening for discard data.

well i also got the torrent test to run finally ... but i dont think the speeds shown are correct ... i get much higher torrent upload and download speeds than shown in the result

Is BitTorrent traffic on a well-known BitTorrent port (6882) throttled?

* The BitTorrent upload (seeding) worked. Our tool was successful in uploading data using the BitTorrent protocol.

* There's no indication that your ISP rate limits your BitTorrent uploads. In our tests a TCP upload achieved minimal 5 Kbps while a BitTorrent upload achieved maximal 282 Kbps. You can find details here.

* The BitTorrent download worked. Our tool was successful in downloading data using the BitTorrent protocol.

* There's no indication that your ISP rate limits your BitTorrent downloads. In our tests a TCP download achieved minimal 187 Kbps while a BitTorrent download achieved maximal 318 Kbps. You can find details here.


Is BitTorrent traffic on a non-standard BitTorrent port (10010) throttled?

* The BitTorrent upload (seeding) worked. Our tool was successful in uploading data using the BitTorrent protocol.

* There's no indication that your ISP rate limits your BitTorrent uploads. In our tests a TCP download achieved minimal 224 Kbps while a BitTorrent download achieved maximal 342 Kbps. You can find details here.

* The BitTorrent download worked. Our tool was successful in downloading data using the BitTorrent protocol.

* There's no indication that your ISP rate limits your BitTorrent downloads. In our tests a TCP download achieved minimal 220 Kbps while a BitTorrent download achieved maximal 217 Kbps. You can find details here.


Is TCP traffic on a well-known BitTorrent port (6882) throttled?

* There's no indication that your ISP rate limits all downloads at port 6882. In our test, a TCP download on a BitTorrent port achieved at least 187 Kbps while a TCP download on a non-BitTorrent port achieved at least 220 Kbps. You can find details here.

* Your ISP possibly rate limits all uploads at port 6882. In our test, a TCP upload on a BitTorrent port achieved at least 5 Kbps while a TCP upload on a non-BitTorrent port achieved at least 224 Kbps. You can find details here.

but the last line of the result was -ve... any idea?

I tried this about a month back, same error.

The server is busy

Finally managed to get though

TCP/Web100 Network Diagnostic Tool v5.5.4b
click START to begin

** Starting test 1 of 1 **
Connected to: 64.9.225.141 -- Using IPv4 address
Another client is currently being served, your test will begin within 405 seconds
Another client is currently being served, your test will begin within 360 seconds
Another client is currently being served, your test will begin within 315 seconds
Another client is currently being served, your test will begin within 270 seconds
Another client is currently being served, your test will begin within 225 seconds
Another client is currently being served, your test will begin within 180 seconds
Another client is currently being served, your test will begin within 135 seconds
Another client is currently being served, your test will begin within 90 seconds
Another client is currently being served, your test will begin within 45 seconds
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 390.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 1.29Mb/s
Your PC is connected to a Cable/DSL modem
Information: Other network traffic is congesting the link
[S2C]: Packet queuing detected

ISP:BSNL Broadband

i finally got the test to run .. but i am getting these errors

Target host TCP configuration test: Fail! [?]
Warning: TCP connection is not using RFC1323 timestamps. [?]
Critical Failure: Did not negotiate window scale, it should be 4. [?]
Diagnosis: The target (client) is not properly configured. [?]
> See TCP tuning instructions at Enabling High Performance Data Transfers [PSC] [?]

any idea?

I am sorry guys , I am really not much into networking so I am not sure what this means.
I will search around google and get you guys some information

The test never worked out successfully for me any time. Always presented me with some errors. So lost interest in it. Surprisingly the test ran fine in the office BSNL connection.