XCancel Is Suspended Again and the Nitter Repo Is Archived
XCancel returns HTTP 451 Unavailable For Legal Reasons with a notice citing a new development in the proceedings. The upstream Nitter repository is now archived.
The WJS Desk
Sep 7, 2026 · updated Sep 14, 2026 · 6 min read
Update, 14 September 2026. XCancel is down again. It returns HTTP 451 Unavailable For Legal Reasons and a suspension notice, and the upstream Nitter repository has been archived. The original piece below, published on 7 September, described it coming back online. That is no longer the situation. What follows the update is unchanged.
What XCancel returns right now
We checked every instance twice from one machine on 14 September. XCancel is not timing out or erroring by accident: it is deliberately serving a 451, the status code reserved for content withheld for legal reasons, with this notice:
Unfortunately, due to a new development in the ongoing legal proceedings, we are required to suspend this service again until further notice. We can't share more details. You can find the content you were looking for on the original website.
"A new development in the ongoing legal proceedings" is the whole disclosure. The first suspension in August was followed by a return once lawyers had looked at the cease and desist. This one is open ended and the operators explicitly say they cannot explain it.
| Instance | Response | Reading |
|---|---|---|
| xcancel.com | 451, twice | Deliberately suspended, with a notice |
| nitter.net | No response | Did not answer from our machine |
| nitter.poast.org | No response | Did not answer from our machine |
| nitter.privacydev.net | No response | Did not answer from our machine |
| lightbrd.com | 403, twice | Reachable, refusing to serve us |
Be careful how you read the middle three rows. A connection that does not complete from one machine is not proof a service is dead worldwide; it can be DNS, routing or a block on our end. The row we are confident about is XCancel, because a 451 with a written notice is a deliberate answer rather than an absence of one.
The upstream project is archived
The more consequential signal is not an instance being down. The
zedeus/nitter repository is archived, last pushed on 7
September, at 14,468 stars. Archived is GitHub's read-only state: no issues, no
pull requests, no further commits.
Instances can come back. A codebase whose author has closed it is a different kind of ending, and it means anyone running an instance from here is maintaining a fork nobody upstream is patching.
How to check for yourself, in one command
The useful check is the status code, not whether the page looks broken:
curl -sI https://xcancel.com/ | head -1What each answer means:
- 451 means suspended for legal reasons. This is the current state, and no amount of waiting or switching networks changes it.
- 200 means it is serving again.
- No response or a timeout is ambiguous. Try from another network before concluding anything.
- 403 means the host is up and declining you specifically, which is usually geography or an IP reputation block rather than a shutdown.
That distinction matters because "is it down" and "is it down for me" are different questions, and only the first one is about XCancel.
X Corp sent cease and desist letters to the developer behind Nitter and the operators of XCancel on August 24, giving them until 5 PM EST the next day to comply. By that evening, nitter.net was offline, XCancel went dark, and the GitHub repository was archived and marked read-only. Two weeks later, the repository is un-archived, the service is back, and three sentences in the README say the project continues.
We read every public statement from both sides, the Hacker News thread with 499 points and 258 comments, and the coverage that piled up in between. The legal advice that turned this around has not been made public, which makes the details worth pulling apart.
What Nitter Actually Is
Nitter is an open-source alternative frontend for Twitter (now X). It pulls public posts and serves them without JavaScript, without tracking, and without an account. XCancel runs a public instance of the same codebase. Between them, they serve users who want to read public posts without handing their browsing data to X's ad infrastructure.
This is the second time Nitter has been forced offline. In January 2024, Twitter killed guest account access, which broke Nitter's data pipeline entirely. The project went dormant until developers found workarounds in 2025 and brought it back. That was a technical shutdown. This time was legal.
What X Claimed
The cease and desist accused Nitter of violating X's terms of service through unauthorized data scraping. Forbes reported that X demanded a permanent takedown of both the live instances and the project's source code repository. The specific legal theories were not disclosed publicly, but the breadth of the demand is notable: X was not asking for a technical fix or a licensing arrangement. It was asking the code to stop existing.
The developer, known by the handle zedeus, posted a brief statement: "nitter.net is offline and development has stopped for the time being. I'm seeking legal advice and won't be commenting further on the specifics for now."
What Happened During the Two Weeks
The GitHub repository went to archived status. XCancel's homepage showed a single line: the service was halted "until further notice." The Hacker News thread exploded. The Register ran coverage headlined "Nitter no more?" and noted the irony of the situation: X, led by a self-described free speech advocate, was using legal threats to shut down a privacy tool, while simultaneously using public X data to train its Grok AI system.
The legal advice, whatever it contained, was apparently decisive. The README was updated with a three-sentence note: "On 24 August 2026, cease and desist letters were sent by X Corp. demanding a permanent takedown of Nitter instances and the project's repository. UPDATE: Following legal advice, the Nitter project will continue. More details will be announced soon."
No further details have been published. We do not know whether the lawyers found a jurisdictional defense, a fair-use argument, or something else entirely. We do know the project did not agree to X's terms and is running anyway.
The Pattern This Fits
X Corp has a history of aggressive moves against alternative clients and frontends. The company revoked API access for third-party apps in early 2023, killing Tweetbot, Twitterrific, and others. It blocked the user-agent strings of alternative browsers that stripped tracking. And now it has tried the legal route against an open-source project that does not use the API at all.
The common thread is control over how people access public posts. X wants every impression to flow through its own interface, where it can serve ads, collect engagement data, and enforce its recommendation algorithm. Every alternative frontend is a leak in that funnel.
Community Reaction
The Hacker News thread pulled 499 points and 258 comments. The dominant reaction was that X's position is legally weak when it comes to scraping public data, especially in jurisdictions outside the US where data scraping law looks different. Several commenters pointed to the hiQ v. LinkedIn ruling in the US, which held that scraping publicly accessible data does not violate the Computer Fraud and Abuse Act.
Others were more cautious, noting that the legal landscape for scraping has shifted since hiQ and that X's terms of service create a contractual layer that sits on top of the statutory one. The fact that Nitter never agreed to those terms (it does not use the API and does not have an account) is the question the legal advice presumably addressed.
The Bigger Picture
The real story is not about one alternative frontend. It is about whether public posts on a social platform can be locked behind a single interface. RSS readers, accessibility tools, academic researchers, journalists, and archival projects all touch the same data that Nitter touches. If X's legal theory holds, all of them are targets. If it does not, the cease and desist was an expensive bluff that backfired by drawing attention to the project.
Nitter's GitHub repository has 1,340 commits. It is back to active status. The README promises more details soon. We will be watching for those details, because whatever legal reasoning got this project back online matters for every tool that accesses public data from a platform that would prefer it did not.
There is also a timing question. The cease and desist arrived during the same month that X began charging enterprise rates for API access to train competing AI systems. The company's enforcement posture on data access is clearly tightening across the board, and Nitter is only the most visible target. Whether the legal advice that brought it back applies to the next project that receives a similar letter is something nobody outside those lawyers knows yet.
