I change it to a more close server in Enid, OK, and the results are indeed a little slower, but not by a large margin. When you run a test, are you changing to other server locations? I'm in NW Oklahoma, and it always points to a Suddenlink server, in Austin, TX. I compared Charleston, WV to the DSL Reports test and got fairly close results, but I'm only trying to pull 200 Mbps. To test past that point, use the browser based version of and manually select another speedtest server in the same city as Suddenlink's. Most commonly that could be CMTS port utilization overload, drop or plant problems.
Suddenlink wifi speed test Pc#
It will show any issue from your PC to that server. You should be able to trust the in-house Suddenlink Speedtest servers as a good test from your modem to the edge of the internal network. The speed test server itself has to be optimized to perform the tests reliably. That makes the test result totally dependent on a 3rd party company's network, and some cases those didn't have the circuit capacity to support a 100 Mbps test, let alone a 1G. The test would have to travel through Chicago, to Pittsburgh, then through a CLEC's network and the other company's network to the server. would select the closest server in WV on someone else's network. Suddenlink WV connects to IXP points in Ashburn, VA (near DC) and in Chicago, IL.
The other problem is with the Ookla Speedtest selected test servers.
I'm in West Virginia, but our customers would test anywhere from Pittsburgh to Seattle and then complain about their speed. Here is why that is a problem and why I went crazy trying to get them installed. I was with Suddenlink several years ago when they had no internal speed test servers.
0 kommentar(er)
