What a ticket and Pokémon proxy brand needs from its supplier

2026-10-27 · Bazyl

If you sell proxies to a ticket group or a Pokémon server, your members don't care about pool size claims. They care about one evening: the on-sale, the restock, the queue. A supplier that's built for scraping can look fine for weeks and fall over the first night your whole server hits the same site at once.

This is the checklist I'd run before putting my name on someone else's network. It's also the list we built ours against, because the team runs that traffic too.

1. Does it hold up when everyone hits at once?

Drop traffic is not spread out. A ticket on-sale puts most of a month's connections into a few minutes, all aimed at the same site.

Ask the supplier what happened on their last big on-sale. A real answer names a date and a fix. A non-answer is "our network is very fast".

We had one of those mornings on 16 September 2026: a ticket on-sale surge ran the European gateway's kernel out of TCP memory. We raised the limits and capped per-connection buffers on all three gateways the same week, and stopped automatic web-server upgrades after one restarted the proxy mid-traffic. That is the level of detail to expect.

2. How long does a sticky session last?

Ticket queues are long. The checkout has to finish on the IP that entered the queue, or the site can drop the purchase.

• Ask for the ceiling in plain numbers. Ours is 24 hours.
• Ask how a member sets it. Ours is one token on the username, so a bot can set it per task.

A brand that sells sticky lines that quietly end after ten minutes will spend every on-sale night in tickets.

3. Can members target a city or an ISP?

Some retailers and ticket sellers treat buyers differently by region. A member who needs a UK home ISP for one site, or a specific city for another, should be able to ask for it in the line itself.

Country-only targeting is fine for monitors. For checkouts, ask for city and ISP targeting, and ask whether it falls back to a wider area when nothing matches. It shouldn't: a silent fallback hands a member a German IP for a UK-only site.

4. Can members read their own errors?

On a drop night, every red line in a bot log becomes a DM to you unless the error explains itself.

Ask what a failure looks like in a bot log. A bare "407" tells a member nothing. A line that says what went wrong lets them tell "my fault" from "retry" without asking you. This is what our own retail gateway answers:

E01 invalid proxy login
E02 no data left on this login
E20 no exit for this targeting, change it or retry
E50 exit failed, retry with a new session

5. Does the supplier stay invisible?

Your members paste lines into bots and post screenshots of their settings. If the hostname or the login prompt names another company, some of your members will go and buy from them directly.

Check three places:

• The hostname. You should be able to use your own.
• The login prompt. Run a request without credentials and read what comes back. Ours names no supplier.
• Emails and dashboards. Your members should never get either from the supplier.

6. Can you start without buying stock?

A new brand doesn't know its demand yet. A supplier that only sells prepaid blocks makes you guess.

Revenue share lets you start with nothing in the bank: your members pay you, the supplier's share comes out of each order, the data lands after payment. Move to a prepaid pool once you know your volume. The zero-capital post has the details.

7. Does the supplier understand the traffic?

The last question is the softest and matters most. When you message them about an AXS queue or a Pokémon Center restock, do they know what you mean?

A supplier whose team runs drops will answer in your language. One that sells to scraping companies will ask you to describe your "use case" in a form.

This matters most on the bad nights. When a site changes how its queue works an hour before an on-sale, you want a supplier who already noticed, not one who needs it explained.

Run the list

Every item above is something you can test before you sell a single line. If you want to run it against us, start with the proxy reseller program and open a ticket in our Discord.