"Rate Limit Exceeded" on X (Twitter): What It Means and How Long It Lasts

You open X, the timeline stops loading, and a grey box says Rate limit exceeded. Most people immediately search whether they've been shadowbanned — the wrong question, which leads to appeal advice that doesn't apply.

The message is a throttle, not a punishment.

What "Rate Limit Exceeded" Means on X

X counts your actions — posts, replies, follows, DMs, and how many posts you load — against per-account caps on a rolling window. Cross a cap, and X stops that action until the window rolls over.

X's About X limits page says the limits exist to "alleviate some of the strain on the behind-the-scenes part of X," and that "if you do reach a limit, we'll let you know with an error message telling you which limit you've hit."

The error is X's rate limiter reporting a number, not a moderator reporting a verdict. Nothing was reviewed; no human decision sits behind it.

The phrase entered everyone's vocabulary on 1 July 2023, when X capped daily reading and thousands of users hit the wall at once. That cap was an emergency setting, and X never republished a read limit — but the error string outlived it, and readers still hit a read wall X does not document.

How Long Does an X Rate Limit Last?

X does not publish a duration. Any page giving you a confident "30–60 minutes for a first offence, 12–48 hours for a repeat" is inventing a tier system X has never described.

What X publishes is the shape of the wait: for time-based limits, "you'll be able to try again after the time limit has elapsed," and for the post limit, "try again in a few hours."

• Read limits — the timeline stops loading — are the ones X never documents at all: no published cap, no published duration.
• Posting limits are the ones X describes in hours, because the daily allowance is split into semi-hourly intervals.
• Daily caps — DMs, follows — need the day to roll over.

X also notes limits "may be temporarily reduced during periods of heavy site usage." If everyone you know is hitting it at once, it isn't your account.

Is a Rate Limit a Shadowban or a Suspension?

No. Three different things — and conflating them is why people appeal something that has no appeal.

	Rate limit	Shadowban	Suspension
What you see	An error naming a limit	Nothing — posts stop reaching people	A suspension notice
Who decided	An automated counter	Ranking systems	Enforcement
How it ends	The window rolls over	You fix the trigger	You appeal
Appeal?	Nothing to appeal	No formal appeal	Yes

The tell is the message. A rate limit announces itself. A shadowban on Twitter never does, which is why you test rather than guess.

What Triggers a Rate Limit on X

The caps X publishes for a standard account:

• Direct Messages: 500 sent per day
• Posts: 50 original posts and 200 replies per day for unverified accounts, split into semi-hourly intervals
• Follows: 400 per day as a technical limit
• Account email changes: 4 per hour

Worth flagging: X's own page contradicts itself — the limits list says 50 posts and 200 replies, while a later paragraph still cites "the post limit of 2,400 updates per day." Plan around the lower figures.

Two are covered elsewhere: the X follow limit explains the 400-a-day cap, the 5,000 ratio and safe unfollow pacing, and our X DM guide covers the message cap. Neither covers the read cap, and X publishes no current figure for it.

The Username-Change Limit Is a Separate, Undocumented Cap

If X rate limited you changing your handle, you hit a counter it does not document — the limits page names email changes, 4 per hour, and says nothing about usernames. Its guide to changing your username covers length rules and warns that your old handle immediately becomes available to someone else, but says nothing about frequency. Treat a handle change as a rare action, not something to experiment with.

What to Do While You Are Rate Limited

Almost nothing, and that's the good news.

1. Stop retrying. Refreshing feeds the counter. Close the tab.
2. Don't log out and back in. It resets nothing and adds attempts to a throttled session.
3. Don't create a second account. An alt is a bigger risk than the limit.
4. Write your drafts anyway. The cap is on sending, not thinking.
5. Don't file an appeal. No action was taken; there's no case to open.

How to Stop Hitting the Limit

• Space out bursts. The allowance is split into semi-hourly intervals, so a pile of replies in one sitting trips a wall the same replies spread across an afternoon never touch.
• Schedule instead of batching by hand. A queue spreads the same volume over hours.
• Cut third-party tools you don't use. X says API requests from every third-party app are tracked against one hourly API limit, so several connected tools reach it faster than one.

Start Posting Within the Limits with Postory

Most rate limits are a pacing problem, not a policy problem. Postory spreads posts across X, Threads and Bluesky on a schedule instead of in bursts.

Once the limit lifts, scan your handle with our free X shadowban test to check nothing else is holding your reach down — a rate limit is loud, and the things that actually suppress reach are quiet.

Try Postory free — schedule across X, Threads and Bluesky instead of posting in bursts.