3 ms·
That said, I can and do get 200mbps+ on fast.com (my preferred/goto speedtest), and still experience constant buffering and the "sorry we can't play that video
by jermaustin1 7y ago
That said, I can and do get 200mbps+ on fast.com (my preferred/goto speedtest), and still experience constant buffering and the "sorry we can't play that video right now" message that kicks me out but then just clicking play again works.
I'm not saying it's their servers or network, but I haven't found a reason for it based on my fast.com results.
- HerrFolgreich 7y ago> but then just clicking pay again works freudian slip much?
- jermaustin1 7y agoGood catch!
- dspillett 7y agoIt may be that your ISP, or another organisation that your traffic flows through, has implemented an efficient and accurate-enough way to identify speed-test traffic from amongst the actual video traffic. Possibly just by assuming that after a few minutes of transfer or a certain amount of traffic, your current use is not likely to be just for speed testing. I assume this is why the tester does not run an upstream test by default: otherwise the lack of a block of upstream traffic would be a good signal that video playing is going on rather than throughput testing.
- jermaustin1 7y agoPossibly. I wouldn't put anything past optimum after they started injecting advertisements for new channels and packages on my non-https traffic.