2 min read
By Mike
Discord Rate Limit: Why Bots Get Slowed Down
A rate limit is Discord's cap on how many requests a bot or user can send in a short time. When a bot goes over it, Discord answers with an HTTP 429 error and a wait time, and the bot has to pause before trying again.
How limits are applied
Every action a bot takes is a request to Discord's API: sending a message, adding a role, editing a channel. Discord counts requests in buckets, usually per route and sometimes per server or channel. There is also a global cap of about 50 requests per second for a bot.
Replies include headers that say how many requests remain and when the bucket resets. A well-written bot reads these and slows down before it is blocked. If it still goes over, the 429 response carries a Retry-After value that says how many seconds to wait.
Why you notice them
- Mass actions such as deleting many messages or changing many roles are slowed on purpose.
- Changing a channel name or topic repeatedly in a short time is limited per channel.
- Adding many reactions or sending bursts of messages triggers short pauses.
To a member this looks like a bot that responds late, not an error. That is the system doing its job.
The serious version: temporary bans
If an app makes too many bad requests, for example thousands of 401, 403 or 429 responses in ten minutes, Discord can block its IP address for a while at the Cloudflare layer. A bot hosted on a shared machine can then fail even though nothing is wrong with your server. Waiting is the only fix.
Never try to get around rate limits with extra accounts or scripts. They exist to protect the platform, and working around them risks a ban.
What you can do as an owner
- Spread large jobs out instead of running them all at once.
- Avoid renaming channels on a timer.
- Prefer bots that queue their requests and respect the limits.
Rate limits and Noxyr
Noxyr's server logs are posted at most every few seconds per channel and ten at a time, so a raid or a large purge never floods the log channel, as described in the server logs docs. Noxyr's own live chat sending is also limited to stop floods. Custom bots have a related rule: every move to a new host is a fresh Discord login, so there is a five-minute wait between moves, see custom bot hosting.
Rate limits also push large bots to split across connections, see sharding. If your bot looks stuck, check the status and ping page first.
Common questions
What does HTTP 429 mean on Discord?
Too many requests. Discord is telling the bot to wait for the time in the Retry-After value before trying again.
Is a rate limit a ban?
No. It is a short pause. Only repeated abuse can lead to a longer temporary block.
Why does my bot reply slowly during a big cleanup?
Bulk actions are rate limited by Discord, so a bot has to spread them out.
