grrr, stumped, but, you indicated an interesting point, which was that you were having audio drops on Team. Your signal levels look ok, but, you can still have cable issues with good looking signal levels. Ok, so, try this, run a ping test to the CMTS, looking for cable signal dropouts.
To do that, run a command line trace to anywhere, google for example:
tracert -4 www.google.com
The first IP will be the modem, the second IP address will be the CMTS. Ping the CMTS for at least an hour. To do that, use:
ping -n 3600 xxx.xxx.xxx.xxx where xxx.xxx.xxx.xxx is the 2nd hop IP address.
To run a longer test, simply increase the "3600" number. Windows pings 1 ping every second, so, 3600 pings will take an hour to complete after which the test will terminate. You can also run an indefinite test using:
ping -t xxx.xxx.xxx.xxx where xxx.xxx.xxx.xxx is the 2nd hop IP address
Use Ctrl c to terminate the test.
When the test is done, copy the bottom results and paste them in a post. To do that, simply select the bottom results area in the command box. Hold the left button down on your mouse when it positioned at the front end of the first results line, and drag down to highlight or select all of the results line. Use Ctrl c to copy them to the clipboard and then Ctrl v or right click ..... Paste to dump the data into a post. I wonder what that might show, if anything. Over the course of a 24 hour test, I'd expect to see no more than about 12 lost packets.
Do a search on Win 10 1809, looks like there were a bunch of network problems, why are you on such an old version anyway? Perhaps you should upgrade, before pulling your hair out on the actual connection.
Do you have any type of QoS running on the network, perhaps it doesn't recognize the data and is slowing it because of being an unknown? or unassigned priority?
Want to add that lately my speed tests on my MAC have show some weird results. I run the Speedtest.net app on a MAC connected to an RT-AC86U which is connected to the CODA 4582 in bridge mode.
I am on the 1000/30 plan. For a number of consecutive speed tests yesterday to the Rogers site my upload would fluctuate between 6 and 25 if I used the default settings. If I disabled IPv6 on my MAC the upload would stay at 32. But more interesting, if I changed the speed test site to Telus or Innsys and used IPv6 I would also get a consistent 32 upload. Which means something appears wrong with the IPv6 speed test to the Rogers site.
As Datalink suggested you should ping the 2nd hop address to see if there's any significant packet loss there.
Not saying you're not throttled, but at least this will help rule out any network issues.
I had my upload issue, but only running the MAC based Speedtest.net app to the Rogers server using IPv6. This behaviour only started a few days ago. Switching to Telus or Innsys gave me my expected upload speed. Did you try servers other than Rogers using IPv6?
By the way, even with IPv6 enabled when you run the speedtest.net app to a Bell server, it will use IPv4. You can see that in the speedtest.net results history.
Also I assume your Asus IPv6 settings follow https://communityforums.rogers.com/t5/Internet/Rogers-IPv6-Status/m-p/373238#M36710