🚨Nitter Instances Rate-Limited After Issue #1442
All Nitter instances hit by rate limits
TL;DR
An issue reported on Aug 25, 2026, has caused all public Nitter instances to be rate-limited. Reactions are unavailable due to the problem, affecting thousands of users.
Nitter instances have been hit with a rate limit error since an issue was opened on August 25, 2026. This affects every instance and has made reactions unavailable for all users. The issue has garnered significant attention, with over 13,500 people starring it as of the report date. If you're using Nitter to access Twitter data without the official app or website, this is a big deal.
Key Points
Issue #1442 opened by user on Aug 25, 2026
Total stars on the issue: 13,500 as of report date
758 forks of the issue have been created so far
Error message displayed to users: 'Instance has been rate limited'
Issue can be viewed at https://web.archive.org/web/20260825143445/https://twiiit.com/
Why It Matters
If you're using Nitter for Twitter data access, this issue affects your workflow. Reactions are down and rate limits hit every instance, impacting thousands of users who rely on Nitter's open-source alternative to the official Twitter app.
Frequently Asked Questions
Why does this matter?
If you're using Nitter for Twitter data access, this issue affects your workflow. Reactions are down and rate limits hit every instance, impacting thousands of users who rely on Nitter's open-source alternative to the official Twitter app.
What happened?
An issue reported on Aug 25, 2026, has caused all public Nitter instances to be rate-limited. Reactions are unavailable due to the problem, affecting thousands of users.
Comments
Be the first to comment
Enjoyed this article?
Get it daily. 7am. Free. Reads in 5 minutes.
Join 3,315 builders reading daily.