Nitter and XCancel Back Online 2026: The C&D Reversal

September 9, 2026 · ThreadGrab

A week ago I wrote the obvious headline: X Corp had sent cease-and-desist letters on August 24, nitter.net went dark, XCancel was showing a "service stopped until further notice" notice, and anyone who depended on the anonymous X readers had to ask what to replace them with. This week that story flipped. Around September 6–7, 2026, Nitter and XCancel came back online — after legal advice — and community trackers reported more working instances than there were before the takedown.

Today's homepage of nitter.net is itself the cleanest primary source. There is no longer a shutdown note pinned at the top. Instead it reads, in the maintainer's own words:

"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. 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." — zedeus, 7 September 2026

XCancel, the largest public Nitter instance, posted a matching line on its /cdclegal page: "XCancel service is resumed following legal progress from Nitter." The Nitter GitHub repository and its maintainer also updated their public statements — a commit dated September 6 is titled "Update README - Nitter lives."

The reversal, with dates

If you only read the archive angle — which is what this site is for — the striking part is how fast this moved. The entire arc fits inside roughly two weeks:

None of this means X gave up. As of today there is still no public statement from X Corp withdrawing the letters, and the maintainer has said an announcement will come "within a week" once more can be revealed. This is a live legal situation, not a settled victory for either side. But for practical purposes the anonymous-reader ecosystem that looked dead on August 28 is reachable again on September 9 — and in more places than before.

Why "more instances than before" is the part to believe

The single most useful signal from this week is not the flagship being back. It is that independence survived the C&D. Nitter was never one server. It is a self-hosted frontend that dozens of operators run, and when the takedown story landed, three things happened at once: existing operators who had quietly kept instances alive got visibility again, new mirrors spun up, and maintained instance lists got updated so people could find them.

By September 5 a Hacker News thread titled "Nitter has more working instances than before the takedowns" (731 points) was pointing at a running tally. The shitter wiki Instances page on Codeberg, edited September 8, enumerates working public instances, XCancel itself, redirectors such as nitt.tr, and several Tor .onion mirrors that are effectively impossible to take down by domain removal alone.

That is the distributed-resilience lesson this whole episode hands to anyone building a capture or reading workflow around public posts: a project can be "killed" and come back with a different name, a dozen operators and better documentation. The reader's problem is not that Nitter dies forever. The reader's problem is that any single entry point can vanish for a week mid-project.

The archiving angle: stop depending on the viewer, keep the record

This is the part that matters for people who save X threads for research, newsletters, republishing or legal discovery. The Nitter/XCancel reversal is a good-news news item, but it does not remove the underlying fragility that motivated the August 28 discussion. It argues the opposite case even harder:

• Viewers are not archives. Rendering a public thread in a browser is not the same as owning a copy of it. When nitter.net was down, every workflow that read through it stopped even though the underlying posts never went away.
• Instance maps churn. The same community that celebrated "more instances than before" is also the one where operators rate-limit, drop off and change addresses. A bookmark is a weak tool; a local file is not.
• Legal status can toggle. Two weeks ago the C&D looked permanent. This week it is paused pending legal advice. Whatever the next toggle is, the cost of being caught on the wrong side of it is the same: your working copy should already be in your hands.

ThreadGrab's answer is deliberately boring: capture the public post as Markdown you control, with provenance headers, and let third-party viewers do whatever they want. The command below pulls a profile's latest posts through ThreadGrab's public, rate-limited API and writes them into a dated Markdown archive:

curl -s https://threadgrab.com/api/profile/USERNAME \
  -H "Accept: application/json" | jq '.' > profile.json

# Turn the JSON into a plain Markdown archive of the latest posts
jq -r '.posts[] | "## " + .author + " | " + .created_at + "\n\n" + .text + "\n"' \
  profile.json > archive-2026-09-09.md

(Rate limit is 10 requests per IP per 60 seconds, so pace a bulk pull.) The point of the exercise is that the file archive-2026-09-09.md does not care whether Nitter is online, offline or rebranded. It is already yours.

The captured JSON also carries the provenance a plain screenshot cannot: an archived_at timestamp, the account name, the platform and the source URL of each public status. That is exactly the kind of record you want if a thread you saved this week later becomes relevant after another viewer disappears:

---
archived_at: 2026-09-09T09:00:00Z
author: creator_account
platform: x
viewer_status: nitter_down_period_ended
source_url: https://x.com/creator_account/status/example
captured_by: threadgrab_api
---

Nothing in that header depends on who won the C&D fight. It records the post, the moment and where it came from — and it survives the next legal toggle, whatever it is.

What to watch next

• The maintainer's announcement. He said more details would come within about a week. The wording of that announcement — whether it references a formal response, a negotiation, or a change of position by X — will tell you whether this is a pause or a real reset.
• Instance availability. Watch the maintained lists rather than any single domain. If instances stay up through the announcement, the ecosystem has effectively absorbed the C&D; if they fall again, treat the reprieve as temporary.
• Whether X escalates. Cease-and-desist letters were step four of the pattern I traced on August 28. The options after that are technical blocks, renewed letters to more operators, or a negotiated outcome. Any of them can move the viewer status again.

The honest caveats

• This is a one-week snapshot. All statuses above are as of September 9, 2026. Nitter and XCancel being online today is not a guarantee about next month.
• The reversal is Nitter's, not X's. The maintainer chose to resume after legal advice. There is no evidence X Corp retracted or dropped the demand.
• "More instances than before" is community-measured. I did not audit every instance uptime myself; I am relaying the HN tally and the maintained list as of September 8. Instance health changes by the hour.
• Legal specifics are unreported. The maintainer's note explicitly defers details. Quotes reproduced here are his public words; I have not inferred the legal basis he was advised on.

Frequently asked questions

Last verified: September 9, 2026. Primary sources: the nitter.net homepage banner dated September 7, 2026; xcancel.com/cdclegal "service is resumed" notice; the zedeus/nitter GitHub commit 1428b4c "Update README - Nitter lives" (September 6) and its README update; the Codeberg shitter wiki Instances page (edited September 8); and Hacker News threads 49571634 ("Nitter has more working instances than before the takedowns", September 5) and 49588988/49589003 (September 6). Quotes are reproduced verbatim from those sources. Because the maintainer has said further details are still to come, the legal foundation of the reversal is not yet public and all availability statuses could change.