What Discord actually counts
- Your bot token, for the limits that matter day to day. Discord publishes a global ceiling of 50 requests per second per bot, plus separate per-route limits. More addresses do not raise either of them.
- Your IP address, when there is no authorisation header. Discord states outright that an unauthenticated request is limited by address instead of by token, which is the case for anything hitting the API before it has a valid token.
- Invalid requests, counted against the address. Responses of 401, 403 and 429 accumulate, and at 10,000 in a ten minute window the address is temporarily cut off from the API entirely. A loop with a stale token can reach that on its own, without any abuse involved.
- Whether the account is a real person driving a real client. Automating a normal user account, what people call a self-bot, is a documented violation that Discord says it actively detects and terminates accounts over.
Which of our products fits which Discord job
Three of these are ordinary infrastructure questions. The fourth is the one people actually arrive looking for, and it has an uncomfortable answer.
| What you are doing | What we would use | Why that one |
|---|---|---|
| Running bots, one or many | Datacenter IPv4 | A bot is a server talking to an API over HTTPS. Nobody grades the address, so buy the cheapest stable one and keep it. |
| Developing against the API | Datacenter IPv4, separate from production | This is the real argument for a proxy here. A bad token in a retry loop can spend the invalid request budget and lock the address out, and you would rather that happened to a $1.50 address than to your office. |
| Reaching Discord where it is blocked | Residential in a nearby country | A connectivity problem rather than a reputation one. Household addresses in the widest range of countries we sell. |
| Running many user accounts | Nothing we will recommend | Automating user accounts breaks Discord’s terms and gets them terminated. We sell addresses, and an address does not make a self-bot allowed or undetected. |
The honest summary is narrower than most pages on this subject. Discord proxies earn their money on infrastructure and on reach, not on making accounts survive things they are not supposed to be doing.
Setting it up
Discord has no proxy setting in the client. The proxy goes into your bot library or HTTP client, or into the system or browser for reaching the service itself.
# A bot in Python, discord.py takes a proxy directly:
bot = commands.Bot(command_prefix="!", proxy="http://login:password@198.51.100.20:50100")
# Plain API calls from your own code:
curl -x http://login:password@198.51.100.20:50100 \
-H "Authorization: Bot $TOKEN" \
https://discord.com/api/v10/users/@me
# Residential gateway, when you need a household address in a given country:
socks5://login_c_DE:password@proxy.sotaproxy.com:10000- Give development its own address. The invalid request budget is spent per address, so a broken loop in testing should not be able to lock production out.
- Voice is UDP and will not travel through an HTTP or SOCKS5 proxy the way REST calls do. Expect to proxy the API side and leave voice alone.
- Check the response headers rather than guessing. Discord returns the remaining allowance and the reset time on rate limited routes, which is cheaper than discovering the limit by hitting it.
- Handle 429 by waiting the time Discord gives you. Retrying immediately is how a rate limit turns into an address level restriction.
What to buy for Discord
Bot work is the main case here and it is also the cheapest. Prices are entry prices and fall with volume.
Datacenter IPv4
from $1.50 per IP per month, 41 countries
For bots and for development. The right answer for almost everything legitimate on this platform.
- The cheapest stable address we sell, and a bot needs nothing more than stability
- Traffic is not metered, so a busy bot costs the same as an idle one
- Cheap enough to give development its own address and keep production safe
- Recognisable as a datacenter, which matters for user accounts and not for bots
- Raises no per-token limit, because those are counted against the bot
Residential proxies
from $2.00 per GB, 220+ countries
For reaching Discord from a network or a country that blocks it.
- Household addresses in more countries than anything else we sell
- Country selection down to the one you need
- Billed by traffic, so occasional use costs little
- A session ends when the household device drops, one hour at most
- Voice traffic is not going through it, so calls will not benefit
ISP proxies
from $2.30 per IP per month, 24 countries
For a small number of legitimate accounts that need a stable home-looking address.
- Registered to a consumer provider and fixed for the whole term
- Traffic is not metered
- Steadier than a residential session, which expires by design
- 24 countries
- Does nothing about the terms of service, which is what actually ends Discord accounts
If you are here to run a farm of automated user accounts, none of these will help you and we would rather say so before you pay. Discord states that it detects self-bots and terminates the accounts, and that decision is made on behaviour rather than on where the connection came from.
Where people go wrong
Buying proxies to raise a bot rate limit
The 50 requests per second ceiling and the per-route limits are counted against the bot token. Spreading one token across ten addresses gives you the same ceiling and a larger bill.
Retrying straight through a 429
Discord tells you how long to wait. Ignoring it turns a routine rate limit into invalid requests, and enough of those restrict the address rather than the token.
Sharing one address between development and production
A test loop with an expired token can exhaust the invalid request budget in minutes and take the live bot down with it. A separate address costs $1.50 a month.
Expecting a proxy to protect a self-bot
Automating a user account is against the terms whatever address it comes from, and Discord says it looks for exactly this.
What a proxy will not do here
It will not raise the limits on your bot, because those follow the token. It will not carry voice traffic. It will not make an automated user account permitted, and it will not hide one from a system that is documented to look for them. What it does do is real and specific: it keeps the address-level restriction away from the connection you care about, and it gets you to Discord from places that block it. That is a smaller promise than this page could make, and it is the one we will stand behind.
Questions people actually type
Does Discord ban by IP?
For the API, yes, in a specific documented way. Too many invalid requests, meaning 401, 403 and 429 responses, and the address is temporarily restricted from the API. Discord puts the threshold at 10,000 in a ten minute window. That is separate from account bans, which follow the account.
Will a proxy raise my bot rate limit?
No. Discord publishes a global ceiling of 50 requests per second per bot plus per-route limits, and all of them are counted against the token. Routing the same bot through more addresses changes nothing.
Which proxy is best for a Discord bot?
A plain datacenter IPv4 address. Your bot is a server talking to an API over HTTPS and nothing is judging where it came from, so pay the least for something stable. Save the money for a second address so development cannot lock production out.
Can I use a proxy for Discord voice?
Not usefully. Voice runs over UDP and does not travel through an HTTP or SOCKS5 proxy the way REST calls do. You can proxy the API side of things, but calls will go direct.
Can a proxy keep a self-bot from being detected?
No, and we will not sell you one on that basis. Discord documents that automating a user account violates its API terms, that it has built detection for it, and that accounts get terminated. The signal it acts on is behaviour, not the address.
Can I use a proxy to reach Discord where it is blocked?
Yes, and this is one of the cleaner reasons to buy one here. A residential address in a country where the service is reachable solves a connectivity problem. Bear in mind it moves the text and API side of Discord, not voice.
Where the claims above come from
Discord documents its limits better than most platforms on this site, including the one that lands on your address. Every number on this page comes from their own pages.
- Discord, rate limits (developer documentation)The global ceiling of 50 requests per second per bot, the per-route limits, the statement that a request without an authorisation header is limited by IP address instead, and the invalid request limit of 10,000 in ten minutes that restricts the address itself. This last one is the reason a proxy is worth anything at all on this platform.
- Discord Community GuidelinesThe rule is one sentence long and leaves no room: do not use self-bots or user-bots, every account must belong to a human rather than a bot. The same page bans selling or buying accounts and bans account-creation tools and token generators outright. Read it before buying addresses for an account farm, from us or from anyone.
- Discord Terms of ServiceThe contractual side: scraping the service with a robot, spider or crawler without written consent is prohibited, as is unauthorised software that modifies the service. None of that depends on how the traffic is routed.