> ## Documentation Index
> Fetch the complete documentation index at: https://docs.proxylane.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Why Pokémon Center is closed on our ISP pools between drops

> On our Retail, Sneakers and Pokémon Center ISP pools, Pokémon Center opens only around scheduled drops. Here is when and why.

On our static ISP proxies, in the **Retail**, **Sneakers** and **Pokémon Center** pools, pokemoncenter.com is closed between drops. Our IP provider opens it only for scheduled drops, starting about **15 to 30 minutes before each drop**, and closes it again after the drop. The exact close time isn't published.

So these pools are meant for drops. They don't work for browsing the site or watching it for restocks between drops.

## ✅  What to do

**1. Find the drop time**

Drop times come from Pokémon Center's own announcements on its site and social accounts.

**2. Start tasks once the site opens**

The site opens about 15 to 30 minutes before the drop time. Start your tasks 15 minutes before the drop. If the site doesn't load yet, wait a few minutes and try again.

**3. Don't watch the site between drops**

Tools that check pokemoncenter.com for restocks every few minutes won't connect between drops.

**4. Order the Pokémon Center pool**

All three pools are closed between drops the same way. The **Pokémon Center** pool is the one we sell for this site, so pick it when you order. Our other ISP pools haven't been tested on pokemoncenter.com, so we don't recommend them for drops.

## 🔒  Why it's closed between drops

Some users kept monitoring the site and sending requests between drops. That traffic got whole IP ranges flagged, and many of them were banned and lost.

Opening the site only around official drops cuts those flags. The IP ranges stay usable for longer, and every customer gets fair access when a drop goes live.

## 🔎  How it looks

Between drops, pokemoncenter.com doesn't open at all. Your bot or browser shows **403**, **CONNECT tunnel failed** or a SOCKS5 connection error. Other websites still open through the same proxy.

> [accordion] Check it yourself with curl
>
> Put your HTTP proxy line into both commands.
>
> ```bash theme={null}
> curl -sS -o /dev/null -w "connect=%{http_connect} http=%{http_code}\n" -x "http://USER:PASS@IP:PORT" https://www.pokemoncenter.com/
> curl -sS -o /dev/null -w "connect=%{http_connect} http=%{http_code}\n" -x "http://USER:PASS@IP:PORT" https://www.pokemon.com/us
> ```
>
> The first command prints **CONNECT tunnel failed, response 403** and `connect=403 http=000`. The second prints `connect=200 http=200`. Between drops, that pattern means the site is in its closed period, not that your IP is broken.
>
> On a SOCKS5 proxy, use `socks5h://` instead of `http://`. The first command then fails with a closed connection.

If the site still fails during a drop window, that's a different problem. Tell us.

> [card] [Blocked during a drop?](https://docs.proxylane.dev/support.md)
>
> Send us the IP, the pool, the time with your time zone and the error. We will check the IP and the network.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.