Proxies for Riot Games are a question about one moment: the moment a Riot account is created. Riot sets both the account's region of residence and its shard, the group of servers it will live on, from your physical location at that moment, and changing either afterwards is a support request with conditions or, for League of Legends, a paid transfer. Everything else people hope a proxy does for a Riot account, from carrying a match to hiding from Vanguard to raising an API limit, it does not do, and this page says so plainly before it explains the part it does.
On the network side, the Riot tickets have a familiar shape. An account created from home that landed on the wrong shard, with a transfer as the only way out. A proxy bought to route a Valorant match that never touched it. A developer who fanned API requests across addresses and hit the same per-key limit on every one. What follows covers how Riot decides region, what a transfer costs, what the Riot Client will and will not route, why the API limit ignores your address, what Vanguard reads, which proxy type fits, and how to set it up. The per-game specifics live in proxies for Valorant and proxies for League of Legends.
What proxies are best for Riot Games?
For creating an account in the region you intend to play from, and for keeping several accounts on separate addresses, residential proxies pinned to that country and held sticky through sign-up and the first sessions. For an account that should sign in from the same place every day, an ISP proxy (static residential). For scraping public pages at volume, rotating residential, never for the API, whose limit follows the key. Datacenter only for reaching the Riot Client on a blocked network. No proxy type carries a match, changes a region after creation, or matters to Vanguard.
Your region is decided when the account is created, by where you are
Riot's transfer FAQ for Valorant states it directly: both your region of residence and your shard are based on your physical location when you created the account. Create an account from the United States and your region of residence is the United States and your shard is North America. The shard decides which servers you queue on, which ranked ladder you climb, and who you can play with. The region of residence decides the store's currency and pricing, which Riot sets by region and adjusts by region, as it did for Latin America and Brazil in 2024.
Afterwards, the two move by different routes. Changing the region of residence means a request to Riot support, and Riot approves it only for specific reasons, such as moving to a new country. Moving a League of Legends account between servers is a paid transfer, listed in RP in Riot's transfer FAQ, 2,600 RP at the time of writing, and Riot has periodically discounted or suspended transfers around large changes. Valorant accounts have had no self-serve transfer, and a region change there runs through the support route.
The consequence for proxies is exactly one thing, and it is real. The address an account is created from is the address that sets its region, so a residential exit in the country you intend to play from is how a new account starts on the right shard and with the right store. It is a decision made once, at sign-up, and it should be made deliberately, because undoing it costs RP or a support case. The rest of an account's life is about consistency: an account that lives in one country and signs in from it every day looks like its owner.
Sign-up
your location at that moment
Region of residence
store, currency, support
Shard
servers and ranked ladder
Changing it later
support request or RP transfer
The Riot Client has no proxy field, and the games are UDP
The Riot Client is the launcher for League of Legends, Valorant, Teamfight Tactics, Legends of Runeterra, and 2XKO. It has no proxy setting. It picks up the operating system's proxy for some of its web traffic, unevenly enough that a system proxy is as likely to break the sign-in as to route it, and the games it launches send their live traffic over UDP. HTTP, HTTPS, and SOCKS4 proxies carry TCP only, and SOCKS5's UDP relaying is something almost no proxy from a list implements, so a match never follows a proxy and a proxy never lowers ping. That catch, and what it means for each game, is covered in detail on the Valorant and League of Legends pages.
What a proxy does carry is the web side: account creation, the account pages, the store, the support site, and the parts of the client that are web requests. That is enough for every job on this page that a proxy can do at all, and it is best done in a browser rather than through the client. Where the client itself has to reach Riot through a network that blocks it, Proxifier can capture the client process and route its TCP traffic, without Riot's support and without carrying the match.
The Riot API is limited per key, not per IP
Developers arrive at this page for a reason that turns out not to be a proxy problem. Riot's developer portal applies rate limits per API key and per region: a development key is allowed 20 requests per second and 100 per two minutes, enforced separately for each regional endpoint, and development keys expire every 24 hours. Production keys come with higher limits through Riot's application process.
Because the limit follows the key, spreading requests across proxies changes nothing; every address hits the same per-key ceiling. That makes Riot different from platforms whose API throttles per address, and it means the honest answer to "proxies for the Riot API" is that you do not need them. Build against the per-key limits, request a production key when a project outgrows the development key, and save the addresses for the web pages the API does not cover.
What Riot checks, and what a proxy touches
Vanguard reads the machine. Riot's kernel-level anti-cheat bans by hardware and account, and on Windows 11 it ties the hardware identity to TPM 2.0 and Secure Boot. It never reads an address, so a proxy is irrelevant to it, and a banned machine stays banned however it is routed. The details are on the Valorant page.
Phone verification is not an IP gate. Ranked play in Valorant requires a verified phone number, and a proxy gives you an address, not a number.
Sign-up location reads the address. This is the one moment Riot reads the address and keeps the answer: region of residence and shard are set from it. A residential address in the intended country is how a new account starts where it should.
Sign-in location is a consistency signal. An account that signs in from a new country draws verification, and hosting ranges draw more of it. A stable residential address in the account's country keeps a sign-in quiet.
Account linking reads the address. Accounts that share a network can be grouped, and one flagged account in a group is a risk to the rest. One clean IP per account keeps them apart.
Region and payment read the account. Store currency and pricing follow the region of residence, and a card from another country on a regional store is refused or flagged before any address matters.
So a proxy governs the address at sign-up and the address at sign-in, and therefore the region a new account gets and whether accounts share a network. It does not carry a match, matter to Vanguard, raise an API limit, or change a region after the fact.
Why people use proxies for Riot Games
- Creating an account in the right region. Someone who lives in one country and plays with friends in another, someone about to move, someone who wants a second account on another shard: the address at sign-up decides it, and a residential exit in that country is the clean way to make the decision. Riot's rules on multiple accounts, and the smurf question, are covered on the League of Legends page; mass account creation for resale is a different thing and against Riot's terms on any address.
- Keeping accounts separate. A main and an alt, a coach's teaching account, a creator's test account, all on one home address, are one group to Riot. One clean IP per account keeps a flag on one from reaching the rest.
- Consistency for an account that lives elsewhere. An account registered in one country and signing in from that country every day looks like its owner, which matters for boosted accounts and for people who travel.
- Regional store research. How RP or VP and bundles are priced in another region is a browser behind a proxy in that region, with payment still decided by the account and the card.
- Reaching the client on a blocked network. Dorms, schools, and offices block Riot's domains, and a proxy tunnels the web side around it. This is the one job a free proxy can do.
- Ping, matches, Vanguard, and the API, which a proxy does not touch. The sections above are the whole answer.
Which proxy type fits Riot Games
Residential proxies are real home connections, pinned to a country and held sticky through sign-up and beyond, so a new account is created from where it should live and signs in from there afterwards. Rotating, they carry public page reads at volume. If the category is new, what is a residential proxy explains the sourcing.
ISP proxies are static residential: one address, yours for as long as you keep it, on always-on hardware. This is the home for an account that signs in every day from the same place, and the tidiest choice for an account created in a country you do not live in.
Datacenter proxies draw Riot's sign-up and sign-in checks on sight, which makes them the wrong tool for account creation and the only tool you need for reaching a blocked page.
Mobile proxies are carrier addresses shared by many phones, the hardest to flag and the heavyweight option for repeated account work that keeps getting flagged. Most Riot setups never need them.
| Riot job | Proxy type | Why |
|---|---|---|
| Creating an account in a chosen region | Residential, pinned to that country, sticky | The sign-up address sets region and shard |
| An account signing in daily | ISP (static residential) | Same clean address at every sign-in |
| Several accounts on one network | Residential or ISP, one IP each | Breaks address-based grouping |
| Regional store research | Residential, pinned to the region | Sees the local price as a local |
| Reaching the client on a blocked network | Datacenter or free | Only the block matters |
| Matches, ping, the API | None | UDP, or a per-key limit |
How to set it up
Account creation and account work. Set the proxy in a browser, one profile per account, with a sticky residential exit in the country the account should belong to. For several accounts, an anti-detect browser keeps each profile's proxy, fingerprint, timezone, and account together; our antidetect browser proxy setup covers the profile side. Create the account there, verify the email there, and keep that profile and that address for every later sign-in, because an account that hops countries after creation draws exactly the check you avoided at sign-up.
The Riot Client. Leave it alone for account work. If the client itself has to reach Riot through a network that blocks it, Proxifier can capture the client process and route its TCP traffic; the match will still connect direct.
Public pages at volume. Rotating residential in your HTTP client, a realistic header set, and a request rate found by measurement; our Python requests guide covers the client side. For the API itself, no proxy, a proper key, and Riot's per-key limits.
Verify every exit first in our proxy checker: country, latency, and whether your real address leaks in the headers. For account creation the country is the number that matters, because Riot keeps the answer.
Account creation and sign-in (one sticky IP per account, in its country):
new account, EUW -> residential sticky, Germany, held from sign-up onward
main, NA -> 198.51.100.110 ISP, US, held
alt, NA -> 198.51.100.111 ISP, US, held
Riot API -> direct, per-key limits, production key when needed
Matches -> direct, UDP, no proxy involved
How many IPs, sticky versus rotating
One sticky address per account, in the account's country, from sign-up onward and held indefinitely: that is the rule for anything that signs in, and rotation has no place under an account. Rotating residential belongs only to public page reads at volume, sized by request rate. Riot's web traffic is small, so the cost is in addresses rather than data, and our pricing is pay-as-you-go with a balance that does not expire.
Free versus paid for Riot Games
A free proxy can get a browser onto Riot's site from a blocked network, and a dead one costs a swap. Our free proxy list re-checks itself every few minutes across 100+ countries, and the proxy checker confirms an entry first. Never create or sign into a Riot account through one: free proxies are almost all datacenter addresses that Riot's sign-up flags on sight, most die within minutes, and an unknown operator sits on the connection while you type a password. The mechanism is in are free proxies safe, and the Valorant and League pages cover what free costs on the account side. Paid residential at $0.44/GB pay-as-you-go with no KYC covers account creation and months of sign-ins for very little, and ISP addresses at $2.70/IP are the home for the accounts you keep.
Where a proxy stops and Riot starts
On a Riot account a proxy governs two addresses: the one at sign-up, which sets the region of residence and the shard for good, and the one at sign-in, which decides whether an account looks like its owner and whether accounts share a network. It does not carry a match, lower ping, matter to Vanguard, get past phone verification, raise an API limit, or change a region after creation, which costs a support case or RP. Ban evasion and account farming break Riot's terms on any address.
For reaching Riot on a blocked network, start free with the free proxy list and the proxy checker. For creating an account in the right region and keeping the accounts you play on, clean residential at $0.44/GB pay-as-you-go pinned to the country and held sticky, or one ISP address per account, is what holds. Choose the country once, at sign-up, and keep the account there.
Sources
- Riot Games Support, Account Transfer FAQ for Valorant (region of residence and shard set by physical location at account creation; changes through support): support-valorant.riotgames.com
- Riot Games Support, Account Transfer FAQ for League of Legends (server transfers priced in RP): support.riotgames.com
- Riot Games Support, LoL price changes 2024 for Latin America and Brazil (regional pricing adjusted by region): support.riotgames.com
- Riot Developer Portal, rate limiting (development key: 20 requests per second, 100 per two minutes, per region; keys expire every 24 hours): developer.riotgames.com