Pokémon Center UK: British exits for release morning

2026-10-29 · Bazyl

This post sets up British residential exits for the UK Pokémon Center store, from the token in the username to the ttl on each task. The thing most people get wrong is the country code: the United Kingdom is gb, and everything else in the setup is easier than that one letter pair.

The UK store lives at pokemoncenter.com/en-gb. It is in English, it prices in pounds sterling, and its releases go live at a set time in the morning, UK time. Everything below is about the proxy side of that morning. What the store does with a request is the store's.

The exit is -cc-gb, on the username

Every targeting choice rides the username as a -key-value token. The country token takes the ISO two-letter code, and for the United Kingdom that code is GB, written in lowercase: -cc-gb.

A rotating line for a restock monitor is the login plus that one token:

eu-residential2.basilproxies.com:2115:USER-cc-gb:PASS

No -sess- token means a new IP on every request. That suits a monitor that polls the product page, and nothing else on this list.

The password never carries a token. Put -cc-gb on the password and the gateway sees a pair it has never issued and answers E01 invalid proxy login. If your login starts with res2_, it predates 27 October 2026 and keeps the legacy format: the docs show it.

Pick the gateway by where the bot runs

We have three gateways and one pool: eu-, us- and ap-residential2.basilproxies.com. The gateway decides how far your first hop travels. The exit country comes from -cc-gb, whichever gateway you dial.

So a bot on a PC in Manchester or a server in Germany uses eu-. A bot on a server in Virginia running the UK store uses us- with -cc-gb, because its first hop is short and the British exit is set by the token. On 1 October 2026 we measured the TCP connect time from a server in Falkenstein, Germany: eu- answered in 7 to 21 ms, us- in 113 to 148 ms and ap- in 167 to 200 ms.

The numbers from your own machine are the ones that count, and you can take them without credentials: the gateway answers the CONNECT with 407, and the handshake time is there either way.

One sticky line per task

Each task that holds a cart or a session needs its own sticky line: the same -sess- id keeps the same exit. Pick the id yourself, up to 32 lowercase letters or digits, and pick a different one for every task.

Here is a morning for a made-up setup of four tasks and one monitor:

# four tasks, four session ids, two hours each
eu-residential2.basilproxies.com:2115:USER-cc-gb-sess-gbtask01-ttl-120:PASS
eu-residential2.basilproxies.com:2115:USER-cc-gb-sess-gbtask02-ttl-120:PASS
eu-residential2.basilproxies.com:2115:USER-cc-gb-sess-gbtask03-ttl-120:PASS
eu-residential2.basilproxies.com:2115:USER-cc-gb-sess-gbtask04-ttl-120:PASS

# the monitor, rotating
eu-residential2.basilproxies.com:2115:USER-cc-gb:PASS

Four tasks pasted onto one session id share one exit address and one session. Four ids are four.

The dashboard generator writes up to 100,000 lines per generation, each with its own id, so you never have to number them by hand. The sticky vs rotating post goes through which task wants which.

Give each session a ttl longer than the morning

-ttl- sets how many minutes a sticky session holds: anything from 1 to 1440, and 1440 (24 hours) is the ceiling. Leave it off and the session lasts 15 minutes, which is shorter than most mornings.

Size it from when the task starts, not from when the release goes live. A task you start at 08:30 for a 10:00 release that you expect to be done by 11:00 needs 150 minutes of life, so -ttl-180 gives it margin. A ttl of 1440 on that task just keeps the address reserved to you all day for nothing.

When a London token is worth the narrower pool

-city-london narrows the exit to London. It needs -cc-gb beside it, and it can't sit next to an -isp- token. The code is the dashboard picker's code, lowercase with no spaces, and on 1 October 2026 the UK list in the picker had 1,254 cities in it.

The cost is supply. Narrow targeting can't fall back: if no London exit is free at that moment, the gateway answers E20 no exit for this targeting, change it or retry and the task gets nothing. Country-wide -cc-gb draws from the whole country.

My rule: no city token unless something in your own setup needs that city, such as an account whose address is in London and that you always run from there. Otherwise the country is precise enough and a lot deeper.

Test at least ten minutes before

A brand-new login can answer 407 or E53 login not ready yet, retry in a minute for its first minute or two while it reaches every gateway. That is not a wrong password. Generate and test the morning's strings well before the release, then leave them alone.

This checks one task's line: same IP twice, and a British exit.

PROXY="http://USER-cc-gb-sess-gbtask01-ttl-180:[email protected]:2115"

curl -s -x "$PROXY" https://api.ipify.org; echo
curl -s -x "$PROXY" https://api.ipify.org; echo
curl -s -x "$PROXY" https://ipinfo.io/country   # want: GB

Two different IPs mean the session isn't holding: pick a new id and run it again. A country other than GB means the token. The full list of checks is in the pre-drop checklist.

If an exit drops mid-morning

A residential IP is a home connection, and home connections go away. If a task's line answers E50 exit failed, retry with a new session, the fix is in the message: a new session id. Retrying the old id won't bring that address back.

Two more things to know while the morning runs. An idle tunnel closes after about 60 seconds of silence, so a task that sits still for longer opens a new connection on the same string, and the session id is what keeps the exit. And when the balance reaches zero, every line stops opening tunnels until you top up, so set /alerts in a DM to the Basil bot before the morning, not during it.

Paying in pounds, and how much to buy

Prices are charged in USD, EUR, GBP or PLN, detected from where you are and switchable at checkout, so a UK buyer can pay in pounds. Pay as you go starts at 1 GB and never expires. In US dollars as of September 2026, 1 GB costs $4.20, 5 to 14 GB cost $3.60 a gigabyte and 15 to 29 GB $3.00.

We don't publish how many gigabytes a morning on any store uses, because it depends on the bot and the page. Buy a few, run one release, and read the per-domain table on the statistics page the day after. That number is yours and it is real.

We answer for the proxy being live and reachable from the UK when you asked for gb. The rest of the morning is between your bot and the store.

The ready-made strings for every Pokémon Center region are on the Pokémon Center page: change the country token to gb and start there.