> It's not banned, it's throttled because google kept abusing backbone networks once their CDNs had started to burn down and claiming that this is totally fine and fixable with direct BGP peerings with ISPs (yeah, right)
> It works just fine on mobile internet connection where traffic shaping is an inherent feature and it only works like shit on broadband where ISPs are only capable of sending TCP RST once the queue is over the limit.
This is not true. The connections to googlevideo are throttled by government-operated DPI, not by ISPs. You can verify this by sending following request from a Russian residential or mobile IP address to a Russian hosting provider Selectel:
curl --connect-to ::speedtest.selectel.ru https://manifest.googlevideo.com/100MB -k -o/dev/null
The request above is not send to Youtube, it doesn't even leave Russia, but it will be throttled because curl uses "googlevideo.com" in SNI field in ClientHello TLS record. DPI detects the SNI and drops the packets. The download speed will be very low, in the range of kilobytes/sec. However, if you remove googlevideo.com domain from SNI and write curl https://speedtest.selectel.ru/100MB -k -o/dev/null
Then the file will be downloaded at full speed, megabytes/sec. It is a request to the same host, to the same IP address, but it is not throttled anymore.Also the information about mobile connection not being throttled is outdated and incorrect. Nowadays mobile connections are throttled as well.
The information that all ISPs voluntarily decided to throttle Youtube is implausible. Why would they throttle the speed to allow their competitors to lure away their clients?