Rate Limit Exceeded on Twitter: What It Means and How Long It Lasts

Nothing about you. "Rate limit exceeded" is the standard answer a server gives when one client asks for too much too fast, and it is not specific to the platform: most large web services return some version of it, usually as HTTP status 429, Too Many Requests, a code standardised in 2012.

On X (formerly Twitter) it reaches ordinary readers through the front door, not the developer door. You open a long thread, tap into a few profiles, scroll their replies, go back, and the feed stops loading with the error sitting where posts should be. No email arrives and no notice appears on your profile. You refresh, it is still there, and that is the part that makes people assume they have been punished.

The notice settles it. An account restriction comes with a message when you log in saying your features are limited, sometimes for a set time with a countdown, so expiry alone proves nothing. A rate limit comes with nothing beyond the error itself. If the app works again twenty minutes later and no such message ever appeared, the system was throttling requests and your account was never the subject.

On 1 July 2023 Elon Musk posted that the platform was applying "temporary limits" on how many posts an account could read per day: 6,000 for verified accounts, 600 for unverified, 300 for new unverified ones. Within hours he posted higher figures twice more, first 8,000, 800 and 400, then 10,000, 1,000 and 500, and framed the move as a response to "extreme levels of data scraping & system manipulation". It was the day reading limits stopped being an API concern and became something a person with a phone could hit before lunch.

The numbers themselves are the least useful part of that episode. The limits were announced in posts, revised twice within hours of the first one, and never settled into a maintained public table. X's help pages have documented daily caps on actions such as posting, following and direct messages for years, and those numbers have been revised, sometimes without announcement. In May 2026 the unverified posting allowance on that page fell to 50 original posts and 200 replies a day, down from 2,400, noticed by users and confirmed by reporters comparing the page with archived copies. So when an article states flatly that the limit today is exactly N, treat it as folklore unless it points at a live X page you can open yourself. As of September 2026, X publishes no current reading figure, and neither does anyone quoting one.

These three produce different symptoms, and telling them apart saves the panic.

Read the wording before diagnosing. "Rate limit exceeded" over a blank timeline is the first case almost every time.

X does not publish a countdown for consumer accounts and the app shows no timer. The developer side is documented: API responses carry `x-rate-limit-limit`, `x-rate-limit-remaining` and `x-rate-limit-reset`, the last a Unix timestamp for when the window rolls over, with windows commonly 15 minutes or 24 hours depending on the endpoint. Nothing equivalent is surfaced in the app. X's help pages offer only rough guidance for actions: a few hours after a posting limit, a day after the daily follow limit, an hour or so after following too many accounts too quickly. For reading they say nothing, so there you are working blind.

What follows is a rule of thumb, not anything X publishes. Wait fifteen minutes without opening the app, then try once. If it loads, it was probably a short window, and you will hit it again at the same scrolling pace. Still blocked after an hour, and you may be behind a longer or daily counter. Still blocked tomorrow after an untouched night, and it is probably not a rate limit at all: look for an account message when you log in, and check whether X is having an outage.

One habit is worth dropping: refreshing does not shorten the wait, and X does not document what happens to attempts made during a block.

Most advice circulating on this error was inherited from other problems and has nothing behind it here.

Logging out and back in is not reported to clear it, and X does not document what the reading counter is attached to. Clearing the cache or reinstalling does not reset a counter that lives on the server. Switching from app to browser lands you on the same account, and X says its posting, following and messaging limits count actions from all devices. A VPN or a new IP address is not reported to make any difference.

Third-party clients are not a route around it either. Twitter cut off the big third-party apps in January 2023 and then banned such clients in its developer agreement, so apps like Tweetbot and Twitterrific, which once offered a different reading path, shut down. Logged-out browsing was walled off separately, on 30 June 2023, a day before the read limits; it was partly restored within days. X's help page says public posts are visible to anyone, with or without an account, and as of September 2026 a direct link to a single post often still opens without signing in, though browsing beyond it tends to hit a sign-in prompt.

Making a second account is the option people reach for last, and it is a poor one. Under the 2023 scheme, brand new unverified accounts carried the lowest allowance of all, so that workaround arrives pre-throttled.

Every large platform limits something, and few keep a clear page explaining the current values. Facebook is the standing example: its friend cap has been argued over for a decade, and whether a 10,000 friends limit is actually possible still gets answered with confident numbers from people quoting each other.

The same vacuum shows up in measurement. Because Meta publishes no official benchmark, what counts as a good engagement rate on Facebook is answered almost entirely by third-party averages, which is why running the engagement rate formula on your own numbers beats adopting a quoted industry figure. Rate limits work the same way. When the owner of a system stays quiet, the silence fills with specifics nobody verified.

If the scrolling behind the error was research for an account you are building, a forced pause is a reasonable moment to look at the growth side instead, and our list of X (Twitter) follower and engagement services sets out what we run for those accounts.

Developers meet this error far more often than readers, and on that side it is a design problem to solve in code. The response comes back as 429 with headers giving the limit, what you have left and when it resets, so the documented handling is to read `x-rate-limit-reset`, sleep until that timestamp, then retry, backing off if needed. One trap deserves naming. X's rate limit page documents only those three headers, but some endpoints also carry a 24-hour cap, and responses posted on X's developer forum show that cap in separate headers, `x-user-limit-24hour-reset` and `x-app-limit-24hour-reset`, next to an `x-rate-limit-reset` for a shorter window. Sleep to the short timestamp and you can wake your job into another 429. Log every header on a 429, and if a 24-hour reset is there, honour that one.

Beyond that the fixes are structural. Cache what you already have. Batch lookups where an endpoint accepts multiple IDs. Spread scheduled jobs so they do not all fire at the top of the hour, and watch `x-rate-limit-remaining` so you slow down before reaching zero. X's API plans have changed several times since 2023, including the pay-per-use pricing launched in February 2026, so check the current rate limit table at docs.x.com instead of trusting a blog post, including this one.

A reader who hits the wall twice in one day is scrolling faster than the platform wants to serve. A script that hits it twice in one minute has a retry loop with no brakes, and that one will keep hitting it forever.

X publishes no countdown for consumer accounts. For actions its help pages give rough guidance: a few hours after a posting limit, a day after the daily follow limit. For reading they say nothing, so you are judging by behaviour: try after fifteen minutes, then after an hour. If a loading error survives an untouched night, it is probably not a rate limit at all, and you should look for an account message when you log in and check for an outage.

You wait. There is no setting to change and no appeal to file, because nothing has been decided about your account. Refreshing does not shorten the wait, so leave the app alone and try again after fifteen minutes, then after an hour. Clearing the cache or reinstalling does not reset a counter held on the server, and logging out or switching IP address is not reported to help.

Reading limits arrived publicly on 1 July 2023, when Elon Musk posted that temporary caps were being applied and described them as a response to extreme levels of data scraping and system manipulation. The announced figures were raised twice more within the same day. Request limits themselves are not new or unusual: they are routine infrastructure protection, and most large platforms apply some version to both apps and APIs.