Proxies for Blizzard: Battle.net Regions, the Launcher, and What a Proxy Can Do

Proxies for Blizzard are really proxies for Battle.net, the account and launcher that sit in front of World of Warcraft, Overwatch 2, Diablo, Hearthstone, StarCraft, and the rest. Each game has its own network story, its own anti-cheat, and its own page on this site. What they share is the Battle.net account, whose country decides more than most players realize, and the Battle.net app, which Blizzard's own support pages tell you not to put behind a proxy. This page is about that shared layer: what the account country controls, what it takes to change it, what Blizzard says about proxies, which games a proxy can actually carry, and where a proxy fits once you know all that.

We keep the network these connections ride on, so the Battle.net tickets land with us, and they share a shape. A proxy bought to move an account to another region, which no address can do. A launcher that would not sign in behind a system proxy, which Blizzard's support article predicted. An Overwatch player who routed the launcher and wondered why the match still came from home. The answer to all three is the same: know which layer you are trying to change before you buy anything.

What proxies are best for Blizzard?

For account and shop work, residential proxies pinned to the account's country and held sticky, or an ISP proxy (static residential) for an account that logs in from the same place every day. For games whose traffic is TCP (World of Warcraft, Hearthstone) the same static address can carry the full session through an OS-level tool. Datacenter only suits reaching the launcher on a blocked network. No proxy type changes the country on a Battle.net account or raises the API limit, and no plain proxy carries Overwatch 2 or a Diablo IV match, which run over UDP.

One account, four things the country controls

The country on a Battle.net account is set at creation, and four things hang off it.

The shop and its currency. The Battle.net shop prices games, expansions, subscriptions, and in-game items by region, and the account's country decides which prices and which currency you see when signed in. Regional shop research from a browser is real work, and the pricing side of specific games is covered on their own pages, such as World of Warcraft for subscriptions and tokens.

Battle.net Balance. Balance is tied to the account's region and currency. It does not move across regions, and a plan that involves buying Balance in one region to spend in another runs into that wall before any address matters.

Which region's servers and data you live on. Blizzard runs separate regions (the Americas, Europe, Asia, with Korea and mainland China under their own arrangements), and a game's characters, progress, and purchases belong to the region they were made in. Support cannot transfer game accounts or game data between regions, which is why "changing region" for WoW or Diablo means starting again in the new one.

Availability. Some games and some purchases are simply not offered in some countries. Diablo Immortal was never released in Belgium or the Netherlands because of their loot box laws, and Blizzard halted new sales and in-game purchases in Russia in March 2022 while leaving existing players able to play. The account's country, not the address, is the first thing those rules check.

Changing the country is a support ticket with paperwork

Blizzard's own article on changing a Battle.net account's country describes a process, not a setting. The change goes through support, and players report being asked for proof of residence such as a utility bill showing the new address or government-issued identification. Some moves are ruled out entirely: an account created outside Korea cannot be changed to Korea, because Korean accounts require a national ID, and accounts cannot be moved into mainland China either; in both cases the answer is a new account in that region. And a change made while you are in a restricted alpha or beta can cost you that progress.

The consequence for proxies is short. No address changes the country on the account, and a proxy that makes an account look like it lives somewhere else only creates a mismatch between the address and the paperwork. What a proxy can do is keep an account's address consistent with the country it is actually registered to, which is the useful, narrower job.

Where a proxy genuinely fits on Battle.net

With the region question answered, the real jobs are narrower and all real.

• Address consistency for an account. An account registered in one country that logs in from that country every day looks like a person. One that logs in from a new country draws Blizzard's suspicious-login checks and, for a boosted account, the flag the customer is paying to avoid. A static residential address in the account's country is the fix, and the per-game pages cover the boosting case in detail.
• Regional shop research. Seeing how the shop prices a game or a bundle in another region is a browser behind a proxy in that region. It is research, not a way to pay that region's price, which the account country and the payment method decide.
• Several accounts on one network. Blizzard links accounts by shared address, and one flagged account in a group is a risk to the rest. One clean IP per account keeps them apart. The per-game gates that a proxy does not solve, such as Overwatch 2's phone requirement, are in proxies for Overwatch.
• Reaching the launcher on a blocked network. Dorms, schools, and offices block Battle.net or its domains, and a proxy tunnels the launcher around the block. This is the one job a free proxy can do.
• Playing TCP games from a chosen address. World of Warcraft and Hearthstone connect over TCP, so a SOCKS5 proxy can carry the full session, which makes an in-region address for a foreign-region account a workable setup. The UDP games cannot be carried, and the next sections explain the split.

What does not belong on the list: the Battle.net APIs. Blizzard's Game Data APIs are limited per client at 36,000 requests per hour and 100 per second, and the limit follows the client credentials, not the address, so proxies do not raise it. Anyone scraping auction house or character data at scale needs Blizzard's process for a higher limit, not more IPs.

Blizzard's official line on proxies, and what it means in practice

Blizzard does not support proxies, and says so. Its support site has an article on disabling proxy settings when the app or a game cannot connect, a dedicated error page for the app being unable to resolve a network proxy, and a general statement that Blizzard does not directly support proxies, firewalls, or routers and refers you to your ISP or hardware maker. The Battle.net app has no proxy field of its own. It picks up the Windows or macOS system proxy for its web traffic, and players have reported for years that it does so unevenly, with the app unable to sign in behind an HTTP proxy that the browser handles fine.

In practice that leaves two routes, both outside Blizzard's support.

A browser for the web side. Shop research, region checks, account settings, and sign-ins are all websites. A browser with the proxy set (an extension like FoxyProxy is the quick way) does all of that without the app being involved, and it is the right tool for most account work.

Proxifier for the app and the TCP games. The launcher's own traffic is TCP, and so are World of Warcraft and Hearthstone, so an OS-level tool like Proxifier can capture the Battle.net app and the game executable and route them through a SOCKS5 proxy. Blizzard will not help you with it, and a proxy that dies mid-session takes the game with it, so this is a job for a static address you own, never a free one.

The per-game catch: TCP games ride a proxy, UDP games do not

The Battle.net account is one thing; the games behind it use different transports, and that decides what a proxy can carry once you are past the launcher.

The pattern is the same one every shooter guide has to explain: HTTP, HTTPS, and SOCKS4 proxies carry TCP only, almost no free SOCKS5 proxy implements UDP relaying, and a UDP game routed "through a proxy" is really connecting direct from your real address while the launcher goes through the proxy. For those games the honest tool for the match is a VPN, at the cost of ping.

What Blizzard checks, and what a proxy touches

Blizzard's enforcement lives in the games, and the account layer adds consistency checks on top.

Anti-cheat bans accounts and hardware. Warden and the per-game systems read what the client does, ban the account, and for serious cases the machine. None of it reads the address, so a proxy does nothing about a ban, and ban evasion breaks the terms on its own. The per-game pages cover each system.

Phone and identity gates are not IP gates. Overwatch 2's phone requirement on new accounts, Korea's national ID, and the proof-of-residence step for a country change are all layers a proxy cannot touch.

Login location is a consistency signal. A sign-in from a country the account has never seen draws a security check and can lock the account until it is confirmed. This is the dimension a proxy governs, and the reason it should be a static address in the account's own country.

Payment and region are checked at purchase. A card from another country on a regional shop is refused or flagged before any address matters, and Balance stays in its region.

Which proxy type fits Blizzard

Residential proxies are real home connections, pinned to a country and held sticky for a session, so an account logs in from where it lives and a shop check looks like a local. For the TCP games they can carry play as well. 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, registered under a consumer ISP and hosted on always-on hardware. This is the home for a main account, a boosted account, or a foreign-region account that should log in from the same place every day, and for a WoW or Hearthstone session that should not drop.

Datacenter proxies draw Blizzard's login checks and fit only the blocked-network case where reaching the launcher is the goal.

Mobile proxies are carrier addresses shared by many phones, the hardest to flag and rarely necessary here.

How to set it up

Match the setup to the layer.

Web and account work. Set the proxy in a browser, one profile per account, with a sticky residential or ISP address in the account's country. For several accounts, an anti-detect browser keeps each profile's proxy, fingerprint, and account together; our antidetect browser proxy setup covers it. Do shop checks, region research, and account settings there, and leave the app alone.

The app and the TCP games. Install Proxifier, add your SOCKS5 proxy with its credentials, and write a rule that sends the Battle.net app and the game executable (Wow.exe, Hearthstone.exe) through it while everything else stays direct. Pick an exit close to the server region you play on, because the proxy's path to the server is added to yours. The World of Warcraft page has the full walk-through.

The UDP games. Route the launcher if you need to, and accept that the match connects direct. For a genuinely geo-blocked client the tool is a VPN.

Whatever the layer, confirm the exit first with our proxy checker: country, latency, and whether your real address leaks in the headers.

One static address per account, in its registered country:
  main (EU account)        ->  198.51.100.60   ISP, Germany, held
  boosted account (US)     ->  residential sticky, customer's own state, held for the job
  shop research            ->  residential sticky, one exit per region checked

Never:
  a rotating pool under a live WoW or Hearthstone session (it drops)
  two accounts on one address (they get linked)

How many IPs, sticky versus rotating

One sticky address per account, matched to the account's country, held indefinitely: that is the rule for anything that signs in, and it is the whole rule for the TCP games, where a rotation is a disconnect. Rotating residential has only a narrow place here, shop research across many regions, sized by how many storefronts you check. Battle.net's login and shop traffic is small, and even a WoW session sips bandwidth, so the cost is in addresses rather than data. Our pricing is pay-as-you-go with a balance that does not expire.

Free versus paid for Blizzard

A free proxy can get the launcher past a dorm or office block, 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 before you try it. That is the whole legitimate use of free here. For anything with a Battle.net login, a free proxy is a datacenter address that draws the security check on sight, dies within minutes, and passes your sign-in through an operator you know nothing about; the mechanism is in are free proxies safe. Paid residential at $0.44/GB pay-as-you-go with no KYC covers account work for very little, and ISP addresses at $2.70/IP are the home for the accounts and sessions you keep.

Where a proxy stops and Blizzard starts

On Battle.net a proxy governs one layer: the address Blizzard's sign-in, shop, and TCP game servers see, and therefore whether an account's location is consistent with its country and whether accounts share a network. It does not change the country on the account, which is a support ticket with paperwork and, for Korea and mainland China, not possible at all. It does not move Balance across regions, transfer characters, raise the API limit, carry an Overwatch 2 or Diablo IV match, or lift a ban. Blizzard does not support proxies, so whatever you route, you route on your own.

For reaching the launcher on a blocked network, start free with the free proxy list and the proxy checker. For accounts, shop research, and the TCP games, clean residential at $0.44/GB pay-as-you-go held sticky per account, or one ISP address per account you keep, is what holds. Register the account where it will live, keep its address there, and read the page for the specific game before you route anything past the launcher.

Sources

• Blizzard Support, Battle.net Account Country/Region Change (support-handled, Korea and mainland China restrictions, no transfer of game data between regions): us.support.blizzard.com
• Blizzard Support, Disabling Proxy Settings: eu.battle.net
• Blizzard Support, Could Not Resolve the Address of Your Network Proxy: us.battle.net
• Blizzard Support, Troubleshooting Firewall Configuration Issues (per-game port lists; Blizzard does not directly support proxies, firewalls, or routers): eu.battle.net
• Blizzard, Game Data APIs documentation (36,000 requests per hour, 100 per second, per client): community.developer.battle.net
• Game Developer, Activision Blizzard, Epic Games, and Take-Two to halt sales in Russia (March 2022): gamedeveloper.com
• Engadget, Blizzard will not release Diablo Immortal in countries with loot box laws (Belgium and the Netherlands): engadget.com