Nitter Rebounds: More Live Instances Now Than Before the Takedowns

Nitter, the privacy-focused alternative front-end for Twitter/X, has quietly recovered from the wave of shutdowns that gutted its public instance network. A community-maintained wiki (hosted on Codeberg under a fork cheekily named ‘shitter’) now tracks more than a dozen operational instances, spanning both clearnet domains and Tor onion services — a larger roster than existed before the takedowns hit. Instances are sorted by health, from fully working to rate-limited to defunct, giving users a live map of where the service still functions.

The revival hinges on operators solving the two problems that killed the earlier generation of instances. The wiki points prospective hosts to guides on harvesting large numbers of session tokens — necessary to sidestep X’s API restrictions and authentication walls — and on structuring an instance to deflect DMCA notices and other legal pressure. A companion repository offers performance-tuning configurations for those running public nodes.

The resurgence is a case study in the resilience of decentralized, self-hosted tooling against platform crackdowns. Rather than a single point of failure, Nitter now survives as a loose federation of independently operated instances that can be spun up faster than they can be shut down. For privacy-conscious users seeking to read X content without tracking, ads, or an account, the practical availability of the service is arguably stronger than it was pre-purge.