You'd want to run "tracert svc1.cdn.shawcable.net", and we'd also need your Unit ID/Address, as the receiver uploads logs of your speed test attempts which would be great to analyze.
The long and short of it - we upgraded our servers to accommodate Crave content in very last October. The "upgrade" was quite the opposite, which was fairly evident immediately. Since then, we've been working with our vendor to address their side of the issues, but I guess we've *also* found that a bunch of content from late last year was corrupted, so the problem was two-fold and made it a lot more complicated to diagnose, address, and have the vendor work with us.
We've been doing extensive testing throughout this year and...
- have identified the corruption issue - anything encoded in 2019 should be fine at this point, but anything problematic from 2018 needs to be escalated on a title by title basis.
- have had the vendor make tweaks on their end - this has shown improvements but has not fixed it 100% it seems.
Last week, a great stride was hit and we're seeing a LOT less errors when streaming is attempted, through our reporting. However, it seems this hasn't improved either of your experiences, unfortunately.
- have you actually tried to stream with the results you're pulling? A little known secret - we used to encode our HD assets starting at 5.0 Mbps. This was reduced to 1.75 Mbps 2ish years ago, after we looked at Netflix and YouTube encoding practices and what we would still deem as "HD".
1.75 Mbps obviously isn't the greatest HD, but adaptive streaming will get you the best quality it can handle with your network. We continue to advertise 5.0 Mbps as "minimum" for HD, as anything encoded prior to the change wouldn't have the lower rate available and would require the full 5.0 Mbps.
I was just curious if, despite your speeds, if you can still at least watch what you want to...