Yesterday Minnesota Public Radio did a story on mapping broadband service in Minnesota. Affordable, high-speed Internet connections are becoming a critical component for educational and economic development throughout Minnesota and the world. Both the Blandin Foundation and the Minnesota Ultra High-Speed Broadband Taskforce are working hard to increase the availability of broadband throughout the state.

Because it isn’t cheap to bring broadband service to rural areas, knowing which areas are most in need is necessary to determine where to best spend limited resources. The Minnesota Commerce Department is working with Connect Minnesota to map Internet connection speeds throughout the state and is promoting the Connect Minnesota Speed Test as a way for consumers to check on the truthfulness of their ISPs. While this is a great goal, there are significant technical problems with the Connect Minnesota Speed Test.

The first problem is the coding and assumptions present in all Ookla speed tests. Because the speed tests assume you are on a DSL or cable connection, they automatically assume a huge asymmetry in upload and download speeds. Therefore, they give false results for any type of connection other than DSL and cable connections. Don’t use this to test the connectivity for your servers colocated at an ISP or your office T1 or Metro Ethernet connection. Our engineers have pulled down 230Mbps to their workstations here at the office and Ookla speed tests are unable to calculate that type of speed.

The second problem is that the Connect Minnesota Speed Test site itself is clearly limited by a 10Mbps connection. No Internet connection ever performs at 100% and there is always going to be some routing and other overhead wrapped around the actual data itself. This type of speed test will always underestimate the actual speed of any given connection. This is an old speed test issue. Internet routing hasn’t changed and all the caveats Peter John Harrison wrote about in his 1999 SpeedTest still apply.

Finally, and here is my major problem with the Connect Minnesota Speed Test, it is coming from a provider and machines in Texas! This means that it isn’t really testing the speed of your Minnesota Internet connectivity (even with all the above provisos) it is testing the speed of your connectivity to some provider in Texas. There is a lot of network between here and Texas. The packets for the speed test are traversing different networks and providers on their way to and from the server in Texas. They may be affected by various routing issues on networks that have nothing to do with your ISP and that your ISP has no control over.

If the Minnesota Commerce Department wants a more accurate picture of broadband connectivity within Minnesota, they need to locate the speed test on a well-connected server within Minnesota.

Of course, anyone who really wants an idea of the speed of their connection should not just be using an Ookla speed test. Basic FTP gives you a much better test to determine how fast you can pull down a file from a remote site. In fact, ipHouse has files on our servers specifically for customer speed tests. More accurate tools exist for calculating bandwidth but they aren’t easy for the average consumer to use. They almost always require command line access on two machines on each side of the connection you are testing. If you are an ipHouse customer and want to know the speed of your connection, just contact our support team and we will let you know the test options available for your connection and how to see bandwidth usage throughout our network.