Twitter Rate Limit Exceeded: What It Means

The short version: "Rate limit exceeded" means X (still called Twitter by most of us) has decided you, your app, or the tool you're using has made too many requests in a set time window and has temporarily cut you off. It is almost never personal, it is almost always fixable, and in most cases it clears itself within 15 minutes to 24 hours. The fix depends on whether you hit it as a human scrolling the app or as a business using the API through a scheduling tool.

What the error means

X runs on a request-based system. Every time you post a tweet, like something, follow an account, refresh your timeline, or pull data through the API, that's a "request" hitting their servers. X caps how many requests any one account, app, or IP address can make within a rolling time window, usually 15 minutes. Go over the cap and you get blocked until the window resets.

This isn't a punishment, it's a traffic system. Think of it like a motorway with a speed limit. You're not being arrested, you're being told to slow down because the road can't take everyone going flat out at once. X enforces this to stop bots, scrapers, and spam tools from hammering their servers, and the side effect is that genuine businesses using automation tools sometimes get caught in the same net.

The three places you'll see this message

• In the app itself when you've liked, followed, or tweeted too fast, usually after a burst of activity in a short space of time
• Through a third-party tool like Buffer, Hootsuite, TweetDeck or a scheduling app, when the app's shared API quota has been used up by everyone relying on it that hour
• Directly from the API if you or a developer you work with has built something that pulls data, such as a sentiment tracker or a mention monitor

A worked example

Say you run a small e-commerce brand and you've just launched a flash sale. You decide to personally like and reply to every single mention of your brand that morning, maybe 40 replies in twenty minutes, plus you're following back new followers as they come in. Twitter's standard limits for a regular account sit around 50 likes per 15-minute window and roughly 400 follows per day, though X changes these numbers without much warning and doesn't publish a full current list anymore. Stack a sale-day burst of replies on top of that, and you can trip the limit well before lunch. The app shows "rate limit exceeded," your replies stop sending, and you assume you've been shadowbanned. You haven't. You've just been too enthusiastic for the system's taste.

Step by step: what to do when it hits

1. Stop what you're doing immediately. Don't keep hitting refresh or retrying the action, that can extend the lockout in some cases
2. Wait at least 15 minutes before trying again, that's the standard window for most consumer-level actions like likes and follows
3. If you're using a third-party scheduler and the error persists past an hour, check the tool's status page, several big scheduling platforms post live updates when X's API is throttling everyone
4. Log out and back in, or clear the app cache on mobile, this sometimes resets a stuck session that's misreporting your usage
5. If it's tied to the API and you or a developer manages a custom integration, check which API tier you're on. Since X overhauled pricing in 2023, the free tier gives very limited read and write access, and a lot of small tools quietly moved to the $100-a-month Basic tier to get workable limits back

The bit most guides skip

Here's what nobody likes to say plainly: if you're seeing this message constantly, the problem usually isn't X's limits, it's that your posting behaviour looks automated even when a human is doing it. Liking dozens of posts in a tight pattern, following and unfollowing the same accounts repeatedly, or replying with near-identical wording across threads all look exactly like bot behaviour from the server's side, because that's what bot behaviour looks like. X isn't trying to catch you specifically, it's running pattern detection at scale and you've matched a pattern. Slowing down isn't a workaround, it's the actual fix, and most people would rather believe it's a glitch than admit their "engagement strategy" reads as spam to a machine.

Why businesses hit this more than individuals

If you manage a brand account with a team, or you run automation through Zapier, Make, or a custom script to auto-post content, you're sharing API quota across every action that tool performs for every client or account it manages, not just yours. A scheduling tool with thousands of users can burn through its allocated rate limit for the hour well before your scheduled post goes out, and you'll see the error even though you personally did nothing wrong. This is one reason agencies and marketing teams increasingly bring in outside help to untangle which tool, tier, or workflow is causing the bottleneck, particularly once automation is layered across several platforms at once. If that's where you've landed, it's worth getting real eyes on your setup through something like an AI consultant for small business rather than guessing your way through X's documentation, which changes more often than most people can keep track of.

What's changed since X took over from Twitter

Under Elon Musk's ownership, the rate limit rules have been tightened, loosened, and tightened again more than once. In July 2023, X briefly capped verified accounts at 6,000 posts viewable per day and unverified accounts at 600, a move widely reported by outlets including the BBC, before quietly walking it back days later after user backlash. The API itself went from largely free to a tiered paid model, and the free tier now offers so little access that most serious automation tools have moved their users onto paid plans just to function reliably. The practical upshot is that "normal" usage levels from two or three years ago can now trip limits that didn't exist before, and a lot of outdated blog posts and Reddit threads are quoting numbers that simply aren't current anymore.

When it's not really a rate limit at all

Sometimes the message is a red herring. If your account has been flagged for suspicious activity, temporarily locked for a security review, or restricted after someone reported you, X sometimes shows a generic rate limit message rather than telling you the real reason, because showing the real reason can tip off bad actors trying to game the system. If the limit never lifts after 24 hours, or you're getting it on actions as simple as scrolling your own timeline, check your account settings for a security notice or locked status rather than assuming it's purely about volume.

Keeping it from happening again

• Spread activity out across the day rather than batching it into short bursts
• Avoid identical or near-identical replies posted in quick succession
• If you use a scheduler, check whether it lets you stagger posting times slightly rather than firing everything at the top of the hour, when demand on the API spikes
• Review your API tier if you or your team run a custom integration, and budget for Basic or Pro access if the free tier keeps throttling you
• Treat "rate limit exceeded" as information, not an emergency. It's telling you to pace yourself, not that something has gone badly wrong

Frequently asked questions

How long does a Twitter rate limit last?

Most consumer-level limits, such as likes and follows, reset on a rolling 15-minute window. API-based limits can vary by endpoint and tier, and in rare cases a lockout tied to a security flag can last 24 hours or longer.

Does rate limit exceeded mean I've been shadowbanned?

No. A rate limit is a temporary volume cap, while shadowbanning (when it happens) affects visibility, not your ability to act. They can feel similar from the outside but they're caused by different things.

Why does my scheduling tool keep showing this error?

Scheduling tools share API quota across every account they manage, not just yours, so you can hit the limit through no fault of your own during busy periods. Check the tool's status page before assuming the fault is on your end.

Can I pay to avoid rate limits on X?

You can reduce how often you hit them by moving to a paid API tier if you run automation, which was priced from around $100 a month for the Basic tier when X overhauled its pricing. For regular app use, there's no paid way to bypass limits, only to use the platform within the pace it expects.