Cox speedtest.net node unreliable?
Has anyone else found the Cox speedtest.net node(s) unreliable?
I am not talking about Cox's own speed test web page, which has a message on it that it is currently not available. But this MIGHT be related.
Note, as well, I have been having some trouble with my WiFi router, and thus the need to frequently test the connection. The trouble with the WiFi router almost certainly has nothing to do with Cox, but thought I would mention. After some time, the Internet connection and restarts periodically, and I get awful connection WiFi speeds to the Internet (but not locally within my network - yea, strange...) but fine wired. I think it MAY have been a bum version of the Asus firmware (actually, I use AsusWrt-Merlin, which is based on the GPL Asus firmware) and I've just updated from what I hope is the bum version. (Based on comments by AsusWrt-Merlin users.)
Anyway... so I figured that connecting to the Cox speedtest.net node in San Diego (I'm in San Diego) would be the best test, so I always choose that server.
But... the first time I try to connect to the Cox server, it always fails.
So, I switch to another server - there are several in San Diego, and it connects. And then I either get a good - or else totally unacceptable - test, but at least it connects. (If unacceptable, then I reboot my router...)
Let's say I get a great result with another server. Now, if I try the Cox server again, this time it connects. And I typically get a better test result than with the alternative server. Which makes sense.
But the Cox server ALWAYS fails on the first try.
One more point of interest: I use Google DNS servers. Wonder if that has something to do with it?
So, it leave me uncertain if I still have a problem with my router after the latest update, or if there is some known problem with the Cox speedtest.net servers.
---
FYI, I refuse to use the Cox DNS servers which are not compliant with the IETF standard, and "break the Internet" by trying to be "helpful" and routing to a search page for non-existent domains rather than properly returning an error code. This might be fine if you are using a web browser, and actually WANT the "help", but it breaks many other services (e.g. non-browsers which use an API) which are expecting to get an error code for non-existent domain rather than being redirected to a different server! So, I use the Google DNS servers, which are, of course, compliant with the standards.
(Yes, it is alleged that you can disable the "help". OK, try it. I double-dog dare you! ;) )
