As noted in our previous post, on 24 August 2026, X Corp. sent cease-and-desist letters demanding the permanent shutdown of Nitter instances and removal of the project’s repository. The main domain, nitter.net, went offline, and development was suspended pending legal advice.
There has since been an update (7th September) on nitter.net:
Following legal advice, the Nitter project will continue. This instance and others will be back up and running shortly. An announcement will be made within a week, once we’re able to reveal more information.
This is unlikely to be the end of the story. What follows may be a prolonged legal saga, with repeated demands and ongoing back-and-forth that make it increasingly difficult for Nitter to operate and maintain its instances. Running an instance is already more challenging, as operators need session tokens from real accounts to bypass the login walls and API restrictions implemented by Twitter/X.
At present, this is positive news, but operating Nitter is likely to become increasingly difficult. The project now faces an ongoing cat-and-mouse game with X, as each attempt to keep instances accessible could be met with new restrictions, countermeasures, or legal challenges.
Working Nitter instances can be found via the following link: https://codeberg.org/mv12star/shitter/wiki/Instances