Server Rate Limits
Legacy Panel Guide. Some parts still apply. Servers created on Bot-hosting typically share an outbound IP address with a small number of other servers (usuall
Updated Jul 7, 2026
Legacy Panel Guide. Some parts still apply.
Servers created on Bot-hosting typically share an outbound IP address with a small number of other servers (usually 2–5).
In some cases, another user on the same IP may exceed usage limits. When this happens, the IP can be temporarily blocked from accessing certain APIs, which may cause errors in your server console.
These errors often appear as an HTML page with a Cloudflare message indicating that access to discord.com has been temporarily restricted.
What you can do:
- This issue is usually temporary and resolves on its own;
- Set up a proxy to redirect requests;
- Try to use the New panel instead: https://bot-hosting.net/
If you are using the discord.js package, you need to listen to REST events to detect when your application is being rate limited.
By default, discord.js handles rate limits internally and retries requests automatically, without notifying you. This means you may not immediately realize when your bot is being limited because no message will be sent to your server console unless you are logging them.
To monitor this, you can listen to REST events and check for specific response codes, such as:
- 403 – Forbidden (access denied)
- 429 – Rate limited
Below is an example of how to listen for REST events and handle these cases:
client.rest.on(RESTEvents.Response, (Req, Resp) => {
if (!(Resp.status === 403 || Resp.status === 429)) return;
console.log('Rate limited!')
});
- "client" is a Client instance
- "RESTEvents" can be imported from discord.js