Latency has nothing to do with maximum speed. You can still have super high ping but fast speeds. Distance might result in large packet loss, because of the multiple node it has to pass through, but parallelized streams easily fix that issue, and current TCP implementation allows increasing the receive window ( I think it does that on its own? Not sure there either ) to make up for large delay connections.
And that 5% is like way off. I don’t remember the numbers, but the x and y’s are something like 80% advertised speeds at 80% of the time, and 50% speed 100% of the time. It’s simply a more exact law, which rather easily fixes ISP complaint about ambiguoutiy on original rules.
The second part being “guessing” is simply because it’s such an easy scripts that I have and will write on my own, and so never bother looking them up or verifying if they work.
A quick Google shows that’s there are the following tools on the first page:
Though I fully admit I spent no time verifying if they work.
As for my expertise, nothing professional, only stuff I’ve tried out on my own and those that we learnt in computer science internet programming class. So if anything you’ve done or experiences indicates a contradiction of what I mentioned, please point it out, and I’ll gladly update my understanding of it.
Edit: oh hey guys don’t downvote him. While the points he makes are potentially incorrect, they are all rather logical points that someone else may make, perhaps from lack of knowledge (or maybe I’m the ones that’s wrong?)
Edit 2 fixed a few words in the first sentence
If you don't have access to a Linux machine to run a cron job using the speedtest-cli, here's in my opinion the next best thing for Windows
http://loggger.com/
It doesn't use the speedtest-cli, or Speedtest itself, and doesn't test upload but rather you tell it to download a certain file at the intervals you want. It logs the download speed and so on.
As for file size, pick something reasonable according to your download speed. With 25Mbps download speed I would for example pick something in the neighbourhood of 50Mbytes, which is about a 15 second download.
If you don't know what file or where to download, you could headover to some Linux ftp mirror that's close to you. For example Debian https://www.debian.org/mirror/list
I did the detective work for you and there's a 51Mbyte file (contents-source.gz) in the /debian/dists/testing/main directory.
Personally I wouldn't do this for any extended period of time or at really frequent intervals. Good netizenship and so on..
Another thing you can do is to just setup a persistent ping going out to something reliable, like Google DNS, using for example PingPlotter. You can test out the advanced version for free for two weeks.
Considering your new ISP is a WISP, using PingPlotter would probably be a better choice and doesn't use much bandwidth. It's basically a visual traceroute and it displays the various hops the ping packets have to travel through and the time it takes, is there packet loss and if there is how much (%) and so on.
Dude, do what I did contact FCC and use something like http://loggger.com/ which you can set to test your speed every 15 minutes etc just and it will show the times it runs like crap also save screenshots of all of it to show and go to suddenlink site and take screen shot of your plan of what your supposed to get for speed. File complaint with FCC with a month or so of these screen shots showing your speed is wrong or frame rate drops anything you can to show its not right and send that all in with the complaint. They will contact suddenstink and they willl be given 30 days to respond to you. Usually a supervisor will end up calling you and its probably same as my issue what happens, is the sales team doesn't think about the fact that one node can only carry so much bandwidth at a time just because its capable of certain speeds for one person doesn't mean every person on the fastest plan can use max speed at same time, so it trys to load balance and it juts get congestion because its more bandwidth than the one node can handle. I can tell you it may take a year for it to get solved but keep doing the logs they will lie on the phone to you and the techs that come to your house cannot even work on the node so you need it ESCALATED to line technicians or supervisor only explain that your node is overloaded and needs to be resectioned or possibly another needs to installed they are expensive so they will try to weasle out of it for sure. But that is what i did and the next step was formal and suddenlink knew they would lose so they finally did it plus in my state its one party consent so i recorded all my phone calls too so just in case i had to go to court i could prove they made promises and did not keep any of them. Just keep at em and keep in contact with the FCC thru the process or it will never be fixed. When I was done they ran fiber out here added a node and resectioned the old one.
I used Loggger last year to gather proof of the same issue for my ISP. You can run speed tests at set intervals which get logged to a CSV spreadsheet. The main program shows you a nice graph over a determined time as well so you can easily see the dips in network performance.
More than likely it's your ISP and not the realm. Does it seem to get worse around 8-10PM?
It's CVC Congestion, more than likely, and it won't just be affecting PoE, though high pings stand out in PoE a lot.
There's a post on the GGG forums about troubleshooting using WinMTR, that's a good guide to seeing if your network is to blame.
The other tool I've taken to using is http://loggger.com/ , it'll run a speed test on a regular interval and show you how your speeds look throughout the day. If you see a big dip around Netflix o'clock, your ISP might be underallocating CVC. Check whirlpool.net forums for your ISP and see if others report the same thing. Also, you can contact your ISP with these troubleshooting details, and best case scenario, more CVC gets allocated and your performance improved.