I had that happen... except that I had been running my HE.net tunnel for years. Did some diagnostics... found that the endpoint I had selected (in Fremont, CA)

I had that happen... except that I had been running my HE.net tunnel for years. Did some diagnostics... found that the endpoint I had selected (in Fremont, CA) was being geolocated by Google as somewhere in an ex-Soviet Bloc country. Changed the endpoint, and YouTube was back up to full speed. I've had more trouble with Comcast deliberately throttling YouTube downloads [0] than I ever had with that HE.net tunnel. [0] I'm in a position where I can verify that it's Comcast's problem... grab the URL for the actual video file (which dictates the CDN location) and wget it at a high-bandwidth site run by a large, independent third party that's not in the business of doing hosting. Notice that the download at the site saturates a 100mbit connection, whereas at home it hardly hits 500kbit/s. Frown.