Situations like that are frustrating, it can be hard to impossible to get someone to understand and acknowledge the problem, let alone fix it. There are multiple possible causes of this.
First, keep in mind that any residential broadband connection is shared and oversubscribed. Typical ISP capacity is oversubscribed by 20-25 times, assuming that subs will not use it all at the same time. This manifests itself in slowdowns in peak hours (5PM to midnight) when everyone is at home streaming UHD videos, or working from home. When downstream capacity is exhausted, it also affects upstream speeds. This depends a bit on QoS and routing algorithms, but it is generally true.
It is likely that nodes close to you are over-congested at the times when you experience slowdowns, this could be your neighbors using the full capacity of their lines, or something else. This can be measured with traceroutes/pings, it would manifest itself as ping spikes or dropped packets at a hop near you.
As to speed tests, Ookla defaults to a server near you, often provided by your ISP. This only measures the speed between those two points. Bandwidth between you and a remote server not owned by your ISP may be totally different, as it depends on your ISPs backbones and peering arrangements with other companies, this could be (and most likely is) much slower than the connection speed between you and your ISP. This could be measured by a speed test that uses a remote server, rather than something close to you geographically.
Unfortunately there is little you can do, other than provide your ISP with evidence of the issue. Your best bet is increasing your speed tier to get a bigger share of the available upstream speed, change ISPs, etc.
It is possible to change the ToS/QoS settings in your packets, but most ISPs will override those: https://www.speedguide.net/articles/...-dscp-wmm-3477
The TCP Optimizer may help a bit in general with your broadband connection, but it will not fix the quality of the line your ISP provides.
Bookmarks