The “rate limit exceeded” error on X means you have performed too many actions in too short a time window and the platform has temporarily blocked further activity. It is not an account suspension, it is not permanent, and it does not affect your followers or content. It just means X has told you to slow down.
Most rate limits clear within 15 to 60 minutes. Understanding what triggers them makes them far less likely to appear in the first place.
What Rate Limiting Actually Is
X processes hundreds of millions of requests per day. Rate limiting is how the system prevents any single user, app, or bot from consuming a disproportionate share of server resources. Every action you take (scrolling, liking, following, sending DMs, refreshing your feed) sends a request to X’s servers. Each action type has a cap within a defined time window. When you hit that cap, X blocks further requests for that action until the window resets.
The caps apply to specific actions, not to your entire account. Being rate limited on following does not prevent you from posting. Being limited on tweet reading does not prevent you from sending DMs. Each action type has its own counter and its own reset timer.
Current Rate Limits in 2026 (Free vs Premium)
X does not officially publish all of its rate limits. The figures below are based on the most current community testing and platform documentation, but X can adjust them without notice.
| Action | Free Account | Premium | Premium+ |
|---|---|---|---|
| Tweet reading | ~1,000/day | ~10,000/day | Unlimited |
| Tweets posted | ~2,400/day | ~2,400/day | ~2,400/day |
| Following | ~400/day | ~1,000/day | ~1,000/day |
| Unfollowing | ~400/day | ~1,000/day | ~1,000/day |
| Likes | ~500/day | ~1,000/day | ~2,000/day |
| DMs (existing contacts) | ~500/day | ~1,000/day | ~2,000/day |
| DMs (new contacts) | ~20/day | ~50/day | ~100/day |
| Search queries | ~50/15 min | ~100/15 min | ~200/15 min |
Hourly soft caps that trigger faster than daily limits: Even within daily limits, acting too quickly in a short window triggers hourly blocks. Community testing shows these soft thresholds:
Following or unfollowing: more than 30 to 50 accounts per hour. Liking: more than 40 to 50 posts per hour. Tweeting or replying: more than 50 per hour. Rapid bursts of identical actions are flagged faster than the same volume spread across the day.
Daily limits reset at midnight UTC, not 24 hours from when you hit the limit. This means if you hit a daily cap at 10 PM, it resets in two hours rather than the next 24.
Why You Hit the Rate Limit
Scrolling through a heavy feed: Reading 1,000 tweets in a session sounds like a lot, but a fast-scrolling session through media-rich timelines can consume that quota in under an hour.
Following or unfollowing in bursts: The daily follow limit is 400 for free accounts, but following 50 accounts in five minutes will trigger the hourly block long before you reach 400.
Liking too quickly: Tapping like on every post while scrolling through a hashtag or Explore feed is the most common trigger for hourly rate limits. X’s system flags rapid sequential likes as bot-like behavior.
Third-party apps making background calls: If you have automation tools, schedulers, analytics apps, or follower trackers connected to your X account, they continue making API calls in the background even when you are not using them. These calls count toward your daily rate limit. This is why accounts sometimes see “rate limit exceeded” despite feeling like they have barely used the platform.
Multiple clients running simultaneously: Using X in a browser tab, on your phone, and through a third-party tool at the same time multiplies your request rate. X tracks requests from all clients tied to your account.
Using a VPN: VPNs do not directly cause rate limits, but appearing to access X from multiple geographic locations in a short period can trigger X’s security systems. This results in a temporary lock similar to a rate limit but from a different system entirely.
Flagged account history: Accounts that have previously violated X’s terms, received warnings, or been temporarily suspended may have permanently reduced thresholds. X does not disclose this, but affected accounts consistently report lower effective limits across all action types.
How Long Does the Rate Limit Last?
| Type of Limit | Reset Time |
|---|---|
| Hourly action block (following, liking) | 15 to 60 minutes |
| Daily reading limit | Midnight UTC |
| Daily action limits | Midnight UTC |
| Repeated violations | 24 to 72 hours |
Important: Continuing to attempt actions while rate-limited can extend the restriction period. If you see the error, stop attempting that action. Close the app or browser tab and wait. Repeated failed attempts are flagged as persistent automated behavior and can push a 15-minute limit into a 24-hour restriction.
How to Fix Rate Limit Exceeded
1. Wait. For most users, waiting 15 to 60 minutes and then resuming normal activity is all that is needed. The limit resets automatically.
2. Stop retrying. This is the mistake most people make. Repeatedly tapping the same button or refreshing the feed while rate-limited extends the restriction. Put the app down.
3. Log out and back in. This refreshes your session token and occasionally clears a rate limit that has already technically reset but has not cleared from your client’s perspective. The complete logout process is covered in the Twitter logout guide.
4. Clear your cache. Cached session data sometimes holds a stale rate-limited state even after the actual limit has reset. Clearing the app cache forces a fresh session. The Twitter cache clearing guide covers how to do this on iOS, Android, and desktop browsers.
5. Switch clients. Web and mobile app rate limits are tracked somewhat independently. If you are rate-limited on desktop, the mobile app may still function and vice versa. Not a guaranteed fix, but it works often enough to try.
6. Disconnect inactive third-party apps. Go to Settings → Security and Account Access → Apps and Sessions → Connected Apps. Revoke access for any tool you no longer actively use. Each connected app makes background API calls that count toward your total.
7. Check X’s platform status. Sometimes what appears as a rate limit error is actually a platform-wide issue. Check Downdetector for X or search on another platform to see if others are reporting the same error before assuming it is account-specific.
Is Rate Limit the Same as Being Shadowbanned?
No. These are completely different systems with different causes and effects.
A rate limit is a temporary action block with a visible error message. It resets automatically. It does not affect your account’s visibility or how your content is distributed.
A shadowban reduces your content’s visibility to others without any notification or error message. You can still post and use the platform normally, but your content reaches fewer people. The guide to removing bot followers covers how bot activity on your account can contribute to both rate limiting and reduced algorithmic reach, which is a separate issue.
The Specific Limits That Catch People Off Guard
DMs to new contacts: The limit of 20 new DM conversations per day for free accounts is far lower than most people expect. If you are reaching out to new people for business purposes, this limit is easy to hit within a short session.
Following: The Twitter follow limit guide covers the full breakdown of following limits, but the hourly soft cap (30 to 50 accounts per hour) is what triggers most following-related rate limits, not the daily 400 limit.
DMs overall: The Twitter DM limits guide covers the full scope of messaging restrictions, including the separate limits for group conversations.
Inactive accounts creating background requests: Old accounts you no longer use but have not logged out of may continue making background requests to X’s servers through mobile sessions. These ghost sessions count against your rate limit. Reviewing and terminating inactive sessions through Settings → Security → Sessions is worth doing. The inactive Twitter accounts guide covers related account management.
Why Does Twitter Have Rate Limits?
Rate limits serve three practical purposes. They prevent bots and automation tools from drowning out human activity on the platform. They protect servers from overload during high-traffic events when millions of users refresh simultaneously. And they reduce data scraping by organizations harvesting X content for AI training and competitor intelligence, which was the explicit stated reason for the mid-2023 limit tightening under Elon Musk.
The 2023 implementation was aggressive (initially 300 tweets per day for free accounts, later raised to 600 and then to the current ~1,000) and created significant user backlash. Current limits are substantially more permissive than the original 2023 caps while remaining stricter than the pre-2023 environment.
Does X Premium Remove Rate Limits?
No. Premium accounts have significantly higher thresholds, not unlimited access (except for tweet reading on Premium+). For most use cases, Premium’s 10x reading limit and 2.5x action limits eliminate the rate limit errors that free accounts encounter during normal usage.
Whether Premium is worth it depends on your usage pattern. Power users, social media managers, and content creators who spend meaningful time on the platform daily find that the higher limits alone justify the cost. Casual users rarely hit free account limits through normal activity.
For Developers: API Rate Limits in 2026
| API Tier | Monthly Cost | Tweets/Month | Requests/15 Min |
|---|---|---|---|
| Free | $0 | 500 | 50 |
| Basic | $100 | 10,000 | 150 |
| Pro | $5,000 | 300,000 | 450 |
| Enterprise | Custom | Custom | Custom |
API rate limit responses return HTTP 429 status with three headers:
x-rate-limit-limit: your cap for the current windowx-rate-limit-remaining: requests remaining in the windowx-rate-limit-reset: Unix timestamp when the window resets
For apps hitting rate limits, implement exponential backoff: pause requests, wait for the reset timestamp, then resume. Retrying immediately on a 429 makes the situation worse and can result in temporary IP-level restrictions.
How to Avoid Rate Limits Going Forward
Space your actions throughout the day. Following 30 accounts over an hour instead of 30 accounts in five minutes produces the same outcome with no rate limit risk.
Reduce connected third-party apps. Audit your connected apps monthly. Each one you keep adds background API overhead even when you are not actively using it.
Avoid simultaneous clients. Using X through a browser, mobile app, and a third-party tool simultaneously multiplies your request rate. Pick one for active sessions.
Stagger bulk actions. If you need to unfollow a large number of accounts, spread it across multiple days rather than attempting it all in one session. The guide to removing bot followers covers how to do a proper follower audit gradually rather than in bulk.
Do not retry on error. When you see the rate limit message, stop. Continuing to attempt actions extends the restriction period.
Frequently Asked Questions
Most rate limits clear within 15 to 60 minutes for hourly action blocks. Daily limits reset at midnight UTC regardless of when you hit them. Repeated violations from automated behavior can result in restrictions lasting 24 to 72 hours.
Third-party apps connected to your account make background API calls even when you are not actively using X. A scheduler, analytics tool, or follower tracker running in the background can exhaust your rate limit before you open the app. Disconnect inactive third-party apps to resolve this.
Not directly, but using a VPN can trigger X’s security systems if your account appears to be logging in from multiple geographic locations in a short period. This results in a security lock rather than a rate limit, but the effect is similar.
No. A rate limit is a temporary action block that clears automatically. A suspension restricts your entire account and requires action to resolve. Rate limits show a specific error message. Suspensions show a different notification and prevent login.
Hitting rate limits occasionally from normal usage does not affect your account health or content distribution. Repeatedly triggering rate limits through aggressive automation can flag your account for “platform manipulation,” which may reduce your algorithmic reach over time.
Daily limits reset at midnight UTC. You can convert that to your local timezone to know when your counters refresh. There is no in-app notification when limits reset; simply try the action again after midnight UTC.
Alex Bennett is an entrepreneur whose practical tips have helped thousands improve their careers and grow with confidence.