Nitter's Resilience: Instance Availability Post-Takedowns

Despite various efforts to remove them, the ecosystem of Nitter instances has actually expanded, with more functional mirrors currently available than there were prior to the major takedown waves.

Important Notice from Codeberg: The platform has updated its Terms of Use. Specifically, projects related to cryptocurrency are no longer permitted on the service.

---

🌐 Current Instance Status

The following tables and lists categorize the current state of the Nitter network. The general trend can be summarized by the formula: $\text{Instances}_{\text{now}} > \text{Instances}_{\text{pre-takedown}}$

🟢 Fully Operational

These instances are currently the most reliable for accessing content.

🔀 Redirectors

These services act as gateways to other working instances.

• https://nitt.tr
• https://twit.0r.cx
• https://xxcancel.com

⚠️ Active but Rate Limited

These are online but may experience intermittent failures due to request caps.

1. https://nt.vern.cc
2. https://nitter.fullex.fr
3. https://nitter.anoxinon.de
4. https://nitter6.kabii.moe
5. https://nitter.zebes.info
6. https://nitter.wisq.net
7. https://nitter.teamqq.de
8. https://nitter.freedit.eu

🔴 Formerly Active / Taken Down

https://xcancel.com https://nitter.poast.org https://nitter.privacyredirect.com https://nitter.tiekoetter.com https://nuku.trabun.org https://nitter.catsarch.com

---

🛠️ Guide for Hosting a Public Instance

If you intend to launch your own public Nitter mirror, there are several critical hurdles to overcome.

Essential Checklist

• Session Tokens: Learn the process for acquiring a high volume of session tokens to avoid immediate blocking.
• Legal Shielding: Implement strategies to evade DMCA notices and other legal threats.
• Performance Tuning: (Optional/Advanced) Optimize your server for higher traffic.

Technical Architecture

The flow of data for a Nitter instance generally follows this path:

Optimization Resources

For those looking to enhance their instance's speed and efficiency, you can utilize specific configurations. You can find these in the following repository: https://codeberg.org/mv12star/shitter-public-instances-customizations

Example Configuration Snippet

Depending on your setup, you might use Nginx or Caddy for rate limiting. A basic conceptual config might look like this:

# Example Nginx Rate Limit
limit_req_zone $binary_remote_addr zone=nitter_limit:10m rate=5r/s;

server {
    location / {
        limit_req zone=nitter_limit burst=10;
        proxy_pass http://nitter_backend;
    }
}

Note: Deleting the "Instances" wiki page is a permanent action and cannot be reversed.