google has been blocking any IP that uses lots of youtube bandwidth, and that means any public instance needs to do IP rotation.
I also heard they began blocking all IPs belonging to some cloud providers.
I run my own invidious instance from my home servr. Only I use it, so it’ll never be blocked, but I don’t have the same anonymity as if using a public instance…
It’s mostly for the benefits of using youtube ad-free without a google account, while having local bookmarks, watch-later, and subscription feed. If that’s your main goal Invidious is really easy to set-up.
Title is kinda misleading. The issue only affects public instances, and it has been an ongoing problem since many months ago. Basically the moment youtube detects lots of traffic from one IP it gets blocked, and need sign-in.
It seems this block just became harder to work around, and they started blocking all IPs from hosting providers, but I’m sure a solution will be found eventually.
If you have a spare laptop/PC/raspberry pi you can host your own invidious in your home. It won’t get blocked, it will be much faster, and you can use options that are usually disabled on public instances (the API and DASH quality).
Then you can add something like tailscale/twingate into the mix to access it outside your home. Self hosted wireguard can also work if your ISP gives you a static IP or you setup a DDNS service. I personally use twingate because I don’t like opening any port in my router.