sodcalculator

10 Tech How-To

Discord Rate Limit: What It Means & How to Fix

Guide 10-43558 · Updated · Step by step

Being rate limited on Discord means you have sent too many messages, friend requests, or other actions in a short time, and Discord has temporarily blocked further actions to protect its servers. The fix is straightforward: stop the activity that triggered the limit and wait for the cooldown to expire, which usually takes a few seconds to a few minutes. This article explains exactly why rate limits happen, how to read the error, and the practical steps to resolve and avoid them.

What Is a Rate Limit on Discord?

Discord rate limits are automated restrictions that control how often you can perform a specific action, such as sending a message, adding a friend, or joining a server. They exist to prevent spam, abuse, and accidental overload of Discord’s infrastructure. When you hit a rate limit, Discord returns an error message, often with a number like 2000 or 429, and tells you to wait a certain number of seconds before trying again.

Rate limits are not a ban or a punishment for normal use. They are a technical safeguard that applies to everyone, from new users to server owners. The key difference is that a rate limit is temporary and automatic, while a ban is a deliberate action by a server moderator or Discord staff.

Why Does Discord Rate Limit Users?

Discord rate limits protect the platform from being overwhelmed by rapid, repeated requests. Without them, a single user or bot could send thousands of messages per second, slowing down the service for everyone. Rate limits also reduce spam, friend-request abuse, and automated scraping of user data.

Common triggers include:

  • Sending more than 5 messages in a short burst (roughly 5 seconds) in a single channel.
  • Adding more than 3–5 new friends in a short period.
  • Joining too many servers quickly (often more than 10–20 per hour).
  • Using a bot that makes too many API calls per second.
  • Repeatedly editing or deleting messages in rapid succession.

Each action has its own threshold, and Discord does not publish exact numbers because they can change based on server load and account history. The important thing is that the limit is per action, not a global cap on your account.

How to Read the Rate Limit Error

When you are rate limited, Discord shows a red error message near the text box or a notification in the app. The message typically looks like:

You are being rate limited. Please wait X seconds and try again.

Sometimes you may see a numeric code, such as 429, which is the HTTP status code for “Too Many Requests.” The number in the message (e.g., “5 seconds”) is the exact cooldown time you must wait. If you are using the Discord API (for a bot), the error response includes a retry_after field with the number of milliseconds to wait.

If you see a rate limit on the desktop app, it usually appears as a small red banner above the message input. On mobile, it may appear as a toast notification at the top of the screen. In both cases, the message tells you how long to wait, and the timer resets each time you attempt the action again.

How to Fix a Rate Limit (Step-by-Step)

The only reliable fix is to stop the triggering action and wait. Here is what to do:

  1. Read the error message – Note the number of seconds it says to wait. Do not close the app; just wait that long.
  2. Stop all related actions – If you were sending messages, stop typing. If you were adding friends, stop sending requests. Any attempt during the cooldown resets the timer.
  3. Wait the full cooldown – Use a timer if needed. Even a single retry before the cooldown ends will extend the wait.
  4. Restart Discord if the timer seems stuck – Sometimes the client does not update the countdown. Fully quit the app (or close the browser tab) and reopen it.
  5. Check your network – A poor connection can cause repeated requests that trigger a limit. Switch from Wi-Fi to mobile data or vice versa, then try again.
  6. If you are using a bot – Review your bot’s code for missing rate-limit handling. The Discord API returns a retry_after value; your bot should wait that many milliseconds before retrying.

If you have waited the full time and still see the error, the rate limit may be on a different action (e.g., friend requests vs. messages). Check which action you were performing and avoid that action for a few more minutes.

Common Mistakes That Trigger Rate Limits

Many users unknowingly trigger rate limits by doing things that seem harmless. The most common mistakes are:

  • Copy-pasting long messages – Sending the same content to multiple channels quickly looks like spam to the system.
  • Using macros or auto-clickers – Automated tools that send messages or add reactions at high speed are a surefire way to get limited.
  • Bulk friend requests – Adding many people at once, especially strangers, is a common trigger.
  • Rapid server hopping – Joining and leaving many servers in a short time can trigger a limit on server joins.
  • Editing messages repeatedly – Each edit counts as a separate API call, so editing a message 10 times in a row can hit the limit.

If you are a server moderator, note that rate limits apply to bots too. A badly coded bot that spams the API can get the entire server’s webhook or bot actions limited.

How to Avoid Rate Limits in the Future

Prevention is easier than waiting out a cooldown. Follow these habits:

  • Space out your actions – Wait a few seconds between messages, especially in busy channels.
  • Limit friend requests – Send no more than 3–5 per hour, and only to people you know.
  • Use Discord normally – Avoid copy-pasting the same message to multiple servers or channels.
  • If you run a bot – Implement proper rate-limit handling using the retry_after field. Libraries like discord.py and discord.js already do this automatically, but custom code may not.
  • Check Discord’s status page – Occasionally, Discord itself has an outage that causes false rate limits. If the error appears for everyone, it is a server-side issue.

For bot developers, Discord’s API documentation lists the official rate limit headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset). Always read these headers and respect the values.

Rate Limits vs. Other Discord Errors

Rate limits are often confused with other errors. Here is how to tell them apart:

  • Rate limit (429) – Temporary, tells you to wait, and resolves on its own.
  • “Missing Permissions” – You lack the role or channel permission to do something; this is a permission issue, not a time issue.
  • “Account Disabled” – A permanent action by Discord staff, not automatic.
  • “Server Verification Level” – You may need to verify your email or phone before sending messages in a new server, which is not a rate limit.

If you see a message that does not mention “rate limited” or “too many requests,” it is likely a different problem. Check the exact wording before assuming it is a rate limit.

Frequently Asked Questions

How long does a Discord rate limit last?

Most rate limits last between 1 and 60 seconds, depending on the action. Message limits are typically 5–10 seconds, while friend request limits can last up to an hour. The error message always tells you the exact wait time, so follow that rather than guessing.

Can I bypass a Discord rate limit?

No, and you should not try. Bypassing rate limits violates Discord’s Terms of Service and can lead to an account ban. The limit is enforced server-side, so there is no client-side trick to remove it. The only legitimate solution is to wait.

Does restarting Discord fix a rate limit?

Restarting the app can help if the client is not updating the countdown, but it does not reset the server-side timer. The cooldown continues regardless of whether you are online. Restarting only helps if the error is stuck on the screen.

Why do I get rate limited even when I send only one message?

This can happen if you have triggered a limit on a different action, such as friend requests or server joins, and the cooldown is still active. It can also occur if your network is retrying the message automatically due to a poor connection. Check the error message for the specific action and wait the indicated time.

Are rate limits the same for bots and users?

No, bots have different (often higher) rate limits than users, but they are still subject to limits. The Discord API documentation specifies separate limits for bot and user endpoints. A bot that exceeds its limit will receive a 429 response and must wait the retry_after time.

Can a server owner remove a rate limit?

No. Rate limits are enforced by Discord’s global infrastructure, not by individual servers. Server owners can only set their own slowmode (a per-channel message delay), which is separate from Discord’s rate limits. If you see a rate limit, only Discord can lift it, and it lifts automatically.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →