Nitter & XCancel alternative: read X free, without logging in

Nitter.net and XCancel, the best-known public Nitter instances, went offline in September 2026 after legal action from X.

6 endpointsX

GET/v1/twitter/profiles/{handle}
Ready

Handle, profile URL or post link — x.com/username/status/… opens the post and its replies. Have an account? Run unlimited lookups in the app

Free · no X account · no signup

A real run. Measured and priced.

Read one public X profile and its timeline, run on 21 Nov 2026 against live public data. The profile and its latest 20 tweets, with no X login.

  1. 01 GET /v1/twitter/profiles/NASA?by=handle

    92,182,304 followers; joined December 2007.

    1 credit, 2.2 s

  2. 02 GET /v1/twitter/profiles/NASA/tweets?limit=20&by=handle

    The 20 newest tweets, replies left out.

    1 credit, 1.5 s

Credits
2
2 calls
Starter pack
$0.028
$14 per 1,000 credits
Scale pack
$0.0033
$1.64 per 1,000 credits
Runtime
3.7 s
Server time, calls one after another

Credits are each route's published price. Dollar figures are those credits at the list rate of each pack. Results and times are from the calls above, made on 21 Nov 2026; live data changes, so a run today returns newer numbers.

Why Nitter stopped working

What happened, from sources we checked in September 2026.

  • Nitter was an open-source front end for Twitter

    It fetched public posts on its own server and showed them without ads, tracking, JavaScript, or an X account. That only worked while X let logged-out visitors read the site. In January 2024 X removed the guest accounts Nitter relied on, and the developer declared the project dead soon after.

  • A comeback, with a catch

    Development resumed in February 2025, but an instance now needed tokens from real, registered X accounts to fetch anything, and those accounts could be rate-limited or banned.

  • Then came the legal letters

    On 24 August 2026, X Corp sent cease-and-desist letters to Nitter and to XCancel, a popular public instance. Both went offline and the GitHub repository was archived. They came back briefly in early September. Then on 11 September the repository was archived again, and in mid-September XCancel suspended its service “until further notice”, citing a new development in the legal proceedings. When we checked on 24 September 2026, nitter.net wasn't loading and XCancel returned an “unavailable for legal reasons” error.

What people used Nitter for, and what to use now

Social Fetch covers the same jobs in a different way: a free viewer for reading, and an API for everything else. Here's the closest replacement for each one.

  • 01

    Read an account's tweets without an X account

    Our free X viewer, also at the top of this page, shows a public account's latest tweets with photos, views and likes, plus its bio, follower counts and verification. No X login and no Social Fetch signup.

  • 02

    Go further back through an account's tweets

    With a free Social Fetch account (100 credits, no card) you can page back through an account's tweets in the dashboard, or call GET /v1/twitter/profiles/{handle}/tweets from code (endpoint details).

  • 03

    Open one tweet or its replies

    GET /v1/twitter/tweets turns a tweet URL into its text, metrics, and media (details). GET /v1/twitter/tweets/replies lists the replies under it.

  • 04

    Search X

    GET /v1/twitter/search runs X search queries, including operators such as from:, since:, and min_faves:. The free advanced search builder writes the query for you without signup.

  • 05

    Follow accounts over RSS

    Monitors take the place of RSS. They check an account on a schedule and send each new tweet to a signed webhook, or let you pull new events as JSON whenever you like. The X webhook guide walks through it.

Nitter instances and mirror lists

Nitter was built to be self-hosted, so there was never one official site. Volunteers ran public instances, and community lists, like the one on the project's GitHub wiki, tracked which ones worked.

Those lists go stale fast. Each instance runs on its own pool of X accounts, and when X rate-limits or bans them the instance starts showing errors or empty timelines, often before anyone updates the list. Operators also shut instances down over hosting costs or legal risk, as happened to nitter.net and XCancel in 2026. A list that was accurate last month can be mostly dead today.

We don't publish a list of live instances because we can't vouch for them. If you try one anyway, remember that whoever runs it sees your IP address and every page you open. Self-hosting is still possible, but the code is now archived, so you'd be running software that no longer gets fixes, with your own X accounts' tokens at risk of a ban.

API endpoints that replace a Nitter instance

For developers: the X and Monitors endpoints that cover what a Nitter instance did, which was reading profiles and tweets and getting notified of new ones.

  • GET /v1/twitter/profiles/{handle}

    Public profile lookup: bio, follower and following counts, and verification. Replaces the Nitter profile page, and you don't need an X login.

  • GET /v1/twitter/profiles/{handle}/tweets

    Recent tweets for a handle, cursor-paginated. Replaces the Nitter timeline.

  • GET /v1/twitter/search

    X search with the usual operators (from:, since:, min_faves:). Replaces Nitter's search page.

  • GET /v1/monitors/sources

    Lists what you can watch, including tweets (twitter.profile.tweets.list), with the minimum interval and a sample event.

  • POST /v1/monitors

    Create a monitor on a profile's tweets. It replaces the RSS feed, with a signed webhook instead of XML.

  • GET /v1/monitors/{id}/events

    Pull new-tweet events as JSON, cursor-paginated, on your own schedule. For teams that would rather poll a feed than run a webhook receiver.

Full API reference

Replacing Nitter in code

If you scraped Nitter or read its RSS feeds from a script, this is the usual order to switch over.

  1. Step 1: Replace the Nitter profile page

    GET /v1/twitter/profiles/{handle} gives you the same bio and metrics a Nitter profile page showed, as typed JSON instead of scraped HTML.

  2. Step 2: Replace the Nitter timeline

    GET /v1/twitter/profiles/{handle}/tweets returns recent tweets, page by page, in the same response shape as every other Social Fetch endpoint.

  3. Step 3: Replace the RSS feed with a Monitor

    Create a monitor on twitter.profile.tweets.list with an interval or cron schedule. It records the existing tweets when you create it, so they don't fire a false event.

  4. Step 4: Pick push or pull

    Attach a webhook endpoint for push, or skip it and pull GET /v1/monitors/{id}/events on your own cadence. A pull-only monitor is the closest thing to how an RSS reader behaves.

  5. Step 5: Budget for credits

    Every profile lookup, tweet page, and monitor check costs that endpoint's normal credits. Plan for it like any metered API.

The full request. Copy it and run it.

Read a profile's recent tweets (the Nitter timeline's replacement). Swap YOUR_API_KEY for a key from your dashboard. The playground fills in auth for the same request.

RequestGET · cURL
curl -sS \
-H "x-api-key: YOUR_API_KEY" \
"https://api.socialfetch.dev/v1/twitter/profiles/NASA/tweets"
Response200 OK
{
"data": {
"lookupStatus": "found",
"profile": { "handle": "NASA" },
"tweets": [{
"id": "2098078917751951729",
"createdAt": "2026-09-10T15:59:29.000Z",
// …
}],
"page": { "hasMore": true }
}
}

Why an API instead of another Nitter instance

  • Nothing to host or patch

    Social Fetch runs the service, so you aren't relying on a volunteer instance that can vanish overnight.

  • A documented, versioned JSON schema

    Your parser keeps working when X changes its pages.

  • Webhooks in place of RSS

    Monitors send a signed webhook and retry failed deliveries 8 times over roughly 21 hours, with every attempt logged.

  • Would rather poll than run a server?

    GET /v1/monitors/{id}/events is a cursor-paginated JSON feed you can read on any schedule.

  • Paid, and public data only

    Lookups cost credits, and the API returns public accounts, never protected ones.

Common questions

What's the best Nitter alternative now that Nitter is down?

It depends on what you used Nitter for. To read a public account's recent tweets without an account, use a free viewer such as our X viewer. To search X, go further back, or follow accounts, use a service that fetches public X data for you, such as the Social Fetch API. Public Nitter instances are too unreliable to depend on right now.

Is Nitter shut down?

For now, effectively yes. X Corp sent cease-and-desist letters to Nitter and XCancel in August 2026. After a brief return in early September, the GitHub repository was archived again on 11 September and XCancel suspended service until further notice. When we checked on 24 September 2026, neither nitter.net nor XCancel was serving pages. That could change, so check the project's GitHub page for news.

Is there a working Nitter mirror list?

Community instance lists still exist, but they go stale quickly: instances break when X limits the accounts they use, and operators shut them down over cost or legal risk. We don't publish a list because we can't verify which instances work on a given day.

Can I view Twitter/X profiles without an account?

Yes, for public accounts. Our free X viewer shows an account's latest tweets plus its bio, follower and following counts and verification, with no X login and no signup. You get 2 free lookups an hour; a free Social Fetch account gives you 100 more with no wait.

Is there a free Nitter replacement for reading tweets?

Yes, for recent tweets. Our free X viewer shows any public account's latest tweets with no X account and no signup. Going further back, search, and new-tweet alerts go through the API, which is pay-per-lookup: you get 100 free credits when you sign up, with no credit card, and credits you buy don't expire.

Does Social Fetch have RSS feeds like Nitter?

No. Monitors do the same job differently: they check an X account on a schedule and send new tweets to a signed webhook, or you pull new events as JSON from GET /v1/monitors/{id}/events.

Can I still self-host Nitter?

The code is still on GitHub, but the repository is archived, so it no longer gets fixes when X changes something. Running an instance also takes tokens from real X accounts, which can be rate-limited or banned.

Can I see protected (private) X accounts?

No. The viewer and the API only return public data. A protected account may show limited profile basics, but not its tweets.

Read X without depending on Nitter

Sign up for 100 free credits, no card needed. Look up a profile in the playground, read its tweets, then set up a monitor if you want new-post alerts.

Just want to read an account's tweets? The viewer at the top of this page needs no X account and no signup.