Testing your Connectivity

 
Welcome to the Brightview Test Server.

This server allows you to test your broadband connectivity and offers tips for troubleshooting your ADSL connection.

Testing the capacity and speed of your broadband connection gives you an idea of what kind of performance to expect and helps you to recognise problems should they occur. The troubleshooting information on this page can also help you in the diagnosis of any issues. This information will be invaluable should you need to contact our Support team.

Please see the FAQ and Support pages for your ISP for further advice and help.

Data Transfer Rate

Test Your Speed Here

If you are experiencing problems with downloads, it can be helpful to test your connection. This allows you to see if the problem with your service, or the remote site you are accessing.

We have provided a test file, which you can download to see how fast your service is running. If this file downloads at a fast, steady rate, you can be sure that your connection is working successfully and that the problem exists somewhere else on the Internet. Check the download speed in your browser or FTP program: you can expect speeds of between 50KB and 60KB per second.

Remember to remove the files and clear your browser cache if you have downloaded the tests before. This will ensure you get an accurately reported speed.

For testing the connectivity quality of your line, or if a Support Agent asks you to download a file, you can use:

Test File 1 - (10MB)
Test File 2 - (100MB)
Test File 3 - (100MB)

Other helpful sites to check your throughput and give you a data rate are:
http://www.dslreports.com/tools

PING

Running the simple PINGs below will help both you and the Support Agent diagnose problems. You should turn off your any firewall before doing this. Remember to turn it back on when you have finished testing.

From your PC DOS prompt or MacTCPWatcher:
Can you PING your own workstation? (127.0.0.1)
Can you PING the assigned Nameservers? 80.189.92.2 or 80.189.94.2
Can you ping something by name? (www.bbc.co.uk for example)

Hint: Set up a continuous PING from your PC to the test server. At the CMD prompt type "ping -t xxx.xxx.xxx.xxx”
It sometimes takes more than 4 pings to bring up the line, and continuous pings do not overload the network.

Remember to quit the ping when have finished testing.

For example:

 
Z:\>ping www.global.net.uk

Pinging www.global.net.uk [80.189.90.17] with 32 bytes of data:

Reply from 80.189.90.17: bytes=32 time=30ms TTL=107
Reply from 80.189.90.17: bytes=32 time=30ms TTL=107
Reply from 80.189.90.17: bytes=32 time=20ms TTL=107
Reply from 80.189.90.17: bytes=32 time=20ms TTL=107

Ping statistics for 80.189.90.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 30ms, Average = 25ms

Z:\>