Nitter instances
Nitter instances status: 1 up, 13 walled or redirecting, 28 gone
Every public Nitter instance we know of, checked by hand with a plain request to the homepage and to a public profile. Bookmark this page instead of an instance; instances do not last.
Checked 2026-09-11 · 42 hosts
1
Serving pages
8
Answering, but walled
5
Redirecting elsewhere
28
Gone
Serving pages
1 host- Up
nitter.tiekoetter.comProfile pages and timelines load for a plain request; expect rate limits under load.
Answering, but walled
8 hosts- Walled
xcancel.comHomepage says service resumed, but profile pages sit behind a browser-verification wall.
- Walled
nitter.privacyredirect.comEvery page is gated by an Anubis proof-of-work check; nothing loads without JavaScript.
- Walled
nitter.catsarch.comHomepage loads, but profile pages answer 429 with an Anubis access-denied page.
- Walled
nitter.spaceCloudflare challenge on every page; a plain request gets 403.
- Walled
lightbrd.comCloudflare challenge on every page; a plain request gets 403.
- Walled
nitter.perennialte.chCloudflare challenge on every page; a plain request gets 403.
- Walled
nitter.lacontrevoie.frReturns a 503 maintenance page from the operator.
- Walled
nitter.projectsegfau.ltRedirects to a Project Segfault login page; needs an account.
Redirecting elsewhere
5 hosts- Redirects
twiiit.comRedirector, not an instance; sends each request to a different Nitter host, and most of those answer with bot challenges.
- Redirects
nitter.czRedirects to twiiit.com.
- Redirects
nitter.42l.frRedirects to nitter.lacontrevoie.fr, which returns 503.
- Redirects
nitter.weiler.rocksRedirects to a d420.de retirement notice.
- Redirects
n.opnxng.comRedirects to the operator's blog post; no Nitter is served.
Gone
28 hosts- Down
nitter.netMain instance; DNS resolves but the server does not answer.
- Down
nitter.kavin.rocksDNS resolves but the server does not answer.
- Down
nitter.itDNS resolves but the server does not answer.
- Down
nitter.tux.pizzaDNS resolves but the server does not answer.
- Down
nitter.woodland.cafeHTTPS does not answer; plain HTTP redirects to a d420.de retirement notice.
- Down
nitter.pussthecat.orgTLS certificate no longer covers this host; plain HTTP redirects to the operator's homepage.
- Down
nitter.in.projectsegfau.ltHTTPS handshake fails; plain HTTP only redirects back to HTTPS.
- Down
nitter.cutelab.spaceHTTPS handshake fails; plain HTTP only redirects back to HTTPS.
- Down
nitter.dcs0.huServes the operator's static landing page; profile URLs return the same page.
- Down
nitter.euDomain is parked and listed for sale.
- Down
nitter.nohost.networkReturns 404 for every path.
- Down
nitter.bird.froth.zoneReturns 410 with a permanent shutdown notice.
- Down
nitter.privacydev.netDNS points to 0.0.0.0; the operator disabled it.
- Down
nitter.moomoo.meDNS points to 0.0.0.0; nothing answers.
- Down
nitter.poast.orgDNS record removed; nothing answers.
- Down
nitter.1d4.usDNS record removed; nothing answers.
- Down
nitter.unixfox.euDNS record removed; nothing answers.
- Down
nitter.esmailelbob.xyzDNS record removed; nothing answers.
- Down
nitter.d420.deDNS record removed; nothing answers.
- Down
nitter.no-logs.comDNS record removed; nothing answers.
- Down
nitter.fdn.frDNS no longer resolves.
- Down
nitter.mint.lgbtDNS no longer resolves.
- Down
nitter.holo-mix.comDNS no longer resolves.
- Down
nitter.lucabased.xyzDNS no longer resolves.
- Down
nitter.ktachibana.partyDNS no longer resolves.
- Down
nitter.snopyta.orgDNS no longer resolves.
- Down
twitter.owacon.moeDNS no longer resolves.
- Down
nitter.salastil.comDNS no longer resolves.
What to use now
If you came here to read one tweet someone linked, you do not need an instance. Paste the link into the tweet viewer and X's official embed renders it. If you came to look at a profile, the Twitter viewer opens the profile's archived snapshots with a year-by-year timeline and the tweets the archive captured, each as an embed. It is not a live timeline. It is also not going anywhere.
If you still want a live mirror, use the ones marked Serving pages above and expect them to rate-limit, wall, or vanish. The redirectors will keep sending you to the last one standing. When the list goes to zero, this page will say so.
FAQ
Straight answers
Are all Nitter instances down?+
Not all, but nearly. On the 2026-09-11 check, 1 instance served real profile pages to a plain request, 8 answered with a verification wall or maintenance page, 5 redirected elsewhere, and 28 were gone. The number that works shrinks after every event and occasionally grows when someone spins up a new host.
Why did nitter.net stop working?+
The main instance was taken down after legal demands from X on August 26, 2026. It had already been fragile since January 2024, when X removed the guest-account mechanism Nitter depended on.
What is twiiit.com?+
A redirector. It keeps its own list of instances and forwards each request to one that answered recently. It only works as long as at least one instance does, and you may land on a walled one.
How do you check an instance?+
A plain HTTPS request to the homepage and to a known public profile, with a 12-second timeout, from a normal residential connection. 'Up' means a real Nitter page came back for the profile. 'Walled' means a Cloudflare, Anubis or similar verification page, a 403, or a maintenance notice. 'Redirects' means the host forwards elsewhere. 'Down' means no answer, a dead certificate, DNS removed, or a parked page.
Can I run my own Nitter instance?+
Technically, but it needs X credentials to work since 2024, and it exposes you to the same terms-of-service and legal risk that closed the public ones. This page does not recommend it.
What should I use instead?+
For a single tweet link, the official embed via the tweet viewer. For a profile, its archived snapshots and captured tweets in the Twitter viewer. Neither is live, and neither can be taken down the way an instance can.
An instance on your list is up now, or one you list as up is down.+
Statuses change daily. The check date is at the top of the page; the list is re-run after every event and at least monthly. If you run an instance and want it listed, use the contact page.
Keep going