documentation/Invidious-Instances.md

5.3 KiB

title description published date tags editor dateCreated
Invidious-Instances true 2021-05-23T16:58:51.441Z markdown 2021-05-23T16:58:48.431Z

Public Invidious Instances:

Uptime History provided by Uptimerobot

Instances API

Note:

Instances using Cloudflare are marked as such. Instances using any type of anti-bot protection are marked as such.

Instances using any type of analytics are marked as such, must be GDPR compliant (if it's usable in the EU), must be CCPA compliant (if it's usable in California), and must respect the AGPL by explaining their changes and by publishing their source code. In short: instances shouldn't run analytics, because it's not worth it.

To be in this list, instances must have been updated in the last month. An instance that hasn't been updated in the last month is considered unmaintained and will be removed from the list.

Warning: Any public instance that isn't in this list is considered untrustworthy. Use them at your own risk.

List of public Invidious Instances (sorted from oldest to newest):

Tor Onion Services:

Rules to have your instance in this list:

  • Instances must have been up for at least a month before it can added to this list.
  • Instances must have been updated in the last month. An instance that hasn't been updated in the last month is considered unmaintained and is removed from the list.
  • Instances must have statistics (/api/v1/stats) enabled (statistics_enabled:true in the configuration file)
  • Instances must be served via domain name.
  • Instances must be served via HTTPS (or/and onion).
  • Instances using any DDoS Protection / MITM are marked as such (eg: Cloudflare, DDoS-Guard...).
  • Instances using any type of anti-bot protection are marked as such.
  • Instances using any type of analytics are marked as such, must be GDPR compliant (if it's usable in the EU), must be CCPA compliant (if it's usable in California), and must respect the AGPL by explaining their changes and by publishing their source code. In short: instances shouldn't run analytics, because it's not worth it.
  • Instances running a modified source code must respect the AGPL by publishing their source code and stating their changes before they are be added to the list, and must publish any later modification in a timely manner.