How do I know if my bot is on a rate-limited node?
If your bot does not show as ready in the Node.js console, or you are seeing HTTP 429 errors, that usually indicates a rate limit.
Other common signs include delayed responses, missing command replies, random API failures, or occasional HTML pages from Cloudflare instead of normal API payloads.
What to check first
- Look at the bot logs for repeated 429 errors or connection retries.
- Confirm the issue happens across more than one command.
- Check whether your code is retrying too aggressively.
- Rule out a temporary Discord-side outage before changing your code.
What can I do about it?
There is very little you can do while the rate limit is active. The main option is to wait for the limit window to reset.
When does it end?
- A few minutes in the best case.
- Sometimes a few hours.
- Rarely, much longer.
If a rate limit lasts unusually long, LemonHost may try to mitigate it, but this is not guaranteed.
What causes rate limits?
- Bots making too many requests too quickly.
- Poorly coded request logic that spams the Discord API.
- Abusive scripts or selfbots.
Because nodes can share an IP, one heavy-abuse workload can also affect nearby workloads.
Important notes
- This is a Discord-side limit, not a LemonHost panel bug.
- Rate limits cannot be manually removed or bypassed.
How to reduce repeat hits
- Throttle command spam from users.
- Cache Discord API results where possible.
- Avoid restarting the bot in tight loops.
- Back off automatically instead of hammering the API again.