@websquadza
Can you check my link to see why my IPTV is running so wonky. I'm on the 1gbit fibre
Initially i thought maybe it's just the stream that was slow or some settings like cache or something... (so i restarted my FireTV4k and my Tenda Router and the Fibre power)
I ran a speedtest and get over 350mbit from my FireTV4K. So the internet speed isn't too bad. However IPTV is not working well at all.
I found it strange that if i switch my FireTV4K to connect to my cellphone's Mobile hotspot LTE (vodacom LTE) which is only 30-35mbit on the speedtest. I get around 30mbit LTE speeds in my area yet it streams fine without any issues on LTE.
I switch back to my Fibre and it's slowness like crazy, it streams video for about 10seconds then pauses. Loads 30seconds then i can watch video for 20seconds then pauses.
Yip exactly the same experience I have had over the years. This was over couple of different ISP's too... But slap the data on the phone on and walla, no more buffering, or freezing etc
Definitely not shaping. I know that sounds like just another line, but check the traceroutes and you won't see a non-router hop. We don't have any devices to shape traffic on the network. To be honest, it's cheaper to buy bandwidth than buy a Sandvine/equivalent box these days..
I suspect, @Napalm and that your issue only starting last week coincides with our upstream's maintenance. One of the changes they made seems to have affected TCP performance - though pinpointing isn't all that easy. It's either something fragmenting packets, or a MTU//MSS issue. Basically, any TCP issue at US level latencies will cause problems (higher latencies highlight TCP issues much more than local issues).
Knowing exact server IPs you're pulling content from helps us trace and see if there's a route issue. Please always keep this in mind.
First things first - eliminate media players (yes, I know it works great off mobile, but the mobile networks also run at a much lower MTU and aggressively clamp MSS) - and media players are generally quite bad at dealing with TCP issues. So try run the stream on a PC. Then Wireshark is your friend; download wireshark and run a monitor on your ethernet port while running a stream (https://en.wikiversity.org/wiki/Wireshark/Start). I'll send you a link on your ticket where you can drop the PCAP results, these are generally large. This will give us some insight and tell us how to resolve the above.
, it became too much of a mission, and an annoyance having to use a proxy, or else it was a mother buffer to use