chadbag
Well-Known Member
Chadbag and All: Keep in mind that most speed tests do the test to the *nearest* POP which could be anywhere from down the street to the next biggest city. Change the 'test server' to something more distant and see what you have.
Yes, and that is what you want. You want to be able to test the "speed" of the connection you are paying for, which is the wire to your house (or the airwaves to your phone). When provider X sells you a 600mbps connection, they are not guaranteeing a 600mbps to the internet (they're not actually guaranteeing anything as they use words like "up to 600mbps"). What they are saying is the link to your house should normally be able to reach those speeds under certain conditions. Once the request and traffic leaves their system you are at the mercy of the backbones providers, systems, etc that your request and traffic flow through, as well as the targets ability to serve the data. (Such home tests
However, with my "connected to the double wireless and through concrete wifi" phone and speedtest app, I changed the target servers to ones in other nearby states etc (larger providers) and the numbers were all in the same ballpark. However my ethernet connected Mac showed much more differences in data depending on what the target was. My Mac on ethernet through Comcast to a local SLC comcast target server was just under 700 mbps. To Cox in Phoenix it was just under 300 mbps, but to Centurylink in Phoenix it was just over 700 mbps. And to Axcelx Tech in Boston was about 365 mbps.
Those are interesting but the number that helps me diagnose my cable connection speed is the one to the local Comcast server.
