Poor and unstable upload speeds
I live stream on Youtube and been having consistent upload speed issues. Doesn't matter what time of day or night it is either. This has been an ongoing intermittent issue where most of the time I ge...
Forum Discussion
Sorry about that, it's been a few years since I worked in the industry. Either way, the first five hops are within the Cox system.
YouTube, Youtube primary ingest server, and Youtube backup ingest serve all look like this. Doesn't matter what time of day it is. Same goes for Meets, which is what I use for guests when doing fundraiser and educational live streams.
Could you force a IPv4 trace instead and show the whole trace? I think IPv6 routing could be different.
Also, I am showing some packet loss on hop 2 which is between modem and router. How are your modem's signal levels? For instructions, what model modem do you have?
Finally, have you tried a VPN by any chance? If that is stable that would rule out hop 2 issues. If it's a routing issue then you in for a support nightmare. I think Cox got rid of Tier 2 and all there is now is Customer Advocate Group(CAG). I think you can only escalate to them via phone. I am hoping I see something in the signal levels that will make me think a technician can handle it.
Here's where it gets interesting. Ran the same test to Cox.net with the first 5 hops being the same . . . no issues. No dropped packets, low latency, low jitter. Again to a speedtest server outside the Cox framework (first 5 hops the same) . . . no issues. Same with Facebook, and a few other sites.
Meanwhile anything going to Youtube, Google Meets, MS Teams etc. looks like what I posted for Youtube.
So depending on which site I'm directing it to, the results for the first 5 hops is vastly different.
BTW, levels at the modem, ground block, and Ped are fine.
The two things I might suggest trying it changing DNS and disabling IPv6 for a day and see if it makes any difference. You can do both on a device level for testing before enabling on your network.
I use openDNS, or Google DNS, so that's not an issue. I did some deeper digging, and their IPv6 handling appears to be the point of failure. The packet loss and latency is pretty much relegated to IPv6. Bad news is their gateway doesn't allow for IPv6 to be disabled. So I guess I'm off to buy a router so I can bypass their service issue.
