Leaderboard

ok cable, nvm - it sorted itself out and i just got two nice 50/5 tests as expected. i had asked twc to downgrade my speed from 100/10 to 50/5 because i could not find any "killer app" worthy of the $120/yr additional expense. after the downgrade, everything seemed to work fine - except your test sight - but now that too is normal.

I started using Testmy.net in 2005 I think it was (though my dad was using it some time before then) and it's had it's ups and downs. Not going to say it's perfect, but I do prefer it over Ookla tests, simply because I hate Flash. (Java as well but that's not to do with Ookla or Testmy.net.) This site also indicates issues you may not immediately suspect. Your OS can have a significant impact on your speed. I was pulling ~30-35Mbps down and ~7-8Mbps up when I got my new Comcast connection, whereas Ookla showed me at ~45-55Mbps down and ~10-12Mbps up. Ran the TCP Optimizer and all of a sudden my Testmy.net speeds were ~40-50Mbps down and ~9-11Mbps up. Because it uses a raw TCP connection it demonstrates the entire structure (all 7 OSI layers, or 4 TCP/IP layers) of your browsers typical internet connection speed. Ookla simulates a perfect world where you have a perfect connection and no browser/configuration/OS bugs. Ookla is very capable at showing your theorhetical maximum, however Testmy.net is going to show you your typical expected throughput, which in my opinion is much more important. Thanks, EBrown

I'd like to be able to filter the Results table by provider.

I tried OpenDNS once. I think these were the same addresses you listed 208.67.x.x, but I can't remember for sure, and for a part of my queries I was redirected to an almost blank page with some error message. A closer inspection revealed it to reside on an OpenDNS server. Not nice. I recall the sytes.net (No-IP) domain was affected, because that is what am using to keep track of a number of IPs. It was not down at the time. I suppose they don't need to actively inject anything once you choose to query their service. A transparent redirection/injection can still take place by the ISP should it choose to pass all traffic to DNS port 53 to another IP address, which is rare but possible.

1. Technically, no. However, foul DNS can cause significant latency initially depending on the ability of the target DNS server to locate the resource record for the chosen destination, as well as DNS injection can cause you to be directed to locations that are not your intended destination. I recommend using Google's DNS 8.8.8.8. I use 4.2.2.2 but apparently there's an article out there claiming not to. You can also use 208.67.222.222, or 208.67.220.220. (I typically setup all four, 8.8.8.8 -> 4.2.2.2 -> 208.67.222.222 -> 208.67.220.220.) 2. That's the list of tests done by other users/connections/people on Verizon FiOS Connections. Thanks, EBrown

I just connected with Windstream in a third location. Seems that their lines are quite variable in what kind of speed you can expect.