Blog
Deep dive· 3 min read

Proxies for Wildberries: why IPv6 opens the storefront but not the data

Wildberries has an IPv6 address, and that is easy to take as the answer: the cheap IPv6 plan will do. But the site and the data live on different names. The storefront answers over IPv6, while the services that deliver prices, stock and product cards publish only IPv4. For monitoring, that decides which plan you need.

In this article
  1. Storefront and data are different names
  2. How to check yourself
  3. Which plan to take
  4. How many threads you need
  5. Your own products and others'
  6. Common mistakes

Storefront and data are different names

A product page in the browser is assembled from several requests. The page itself comes from wildberries.ru, while price, stock and attributes load as separate JSON responses from other names: search, product cards, storage for photos and descriptions. Price monitoring works with these responses, because they are lighter than the page and change exactly where the price changes.

IPv6 reachability is decided per name: it needs an AAAA record in DNS. We checked the main names on 9 November 2026 through two independent resolvers.

text
# Checked 9 November 2026, resolvers 1.1.1.1 and 8.8.8.8, answers matched
#
# NAME                      AAAA
  wildberries.ru            yes
  www.wildberries.ru        yes
  card.wb.ru                no
  search.wb.ru              no
  basket-01.wbbasket.ru     no

The conclusion is simple: an IPv6 proxy opens the storefront, while requests for data never get past name resolution. In logs this looks like a connection or DNS error, not a block, which is why it is often blamed on the proxy.

How to check yourself

The table above describes a moment, not a rule: an operator can add AAAA any day. Check the names your code actually calls. The browser's network tab on a product page gives you the list.

bash
for h in wildberries.ru card.wb.ru search.wb.ru; do
  printf '%-24s %s\n' "$h" "$(dig +short AAAA "$h" | grep : | head -1)"
done
# Empty column = no AAAA = the name is unreachable over IPv6

The same check for other platforms is in the IPv6 reachability table: by it, Ozon, Avito and hh.ru work over IPv4 only.

Which plan to take

  • Monitoring prices, stock and search results: rotating IPv4. Data requests are independent, and the wider they spread across addresses, the lower the rate per address.
  • A long scenario in one session, for example with a cart: timed rotation or a static address.
  • Storefront only, for example checking that a page opens: IPv6 is enough.

How many threads you need

The math is the same as for any catalog: number of items times update frequency, converted to requests per second and multiplied by average response time. Formulas and examples are in the article on marketplace price monitoring. The platform's limit is set per address, so adding threads without widening the pool only speeds up refusals.

Your own products and others'

For their own products, sellers have the official Wildberries API: getting prices, stock and orders from it is more reliable and fairer than from pages. Proxies are for what the API doesn't cover: competitors' prices, search positions, stock at other sellers. Keep the pace reasonable: the platform may limit frequent requests, and we don't promise it won't.

Common mistakes

  • Checking reachability on the home page and buying IPv6. The home page opens, while data requests fail at name resolution.
  • Adding threads instead of widening the pool. The platform counts the rate per address, so more threads on the same addresses hit the limit sooner.
  • Keeping one connection for thousands of requests. With per-request rotation the address changes only with a new connection, and keep-alive pins it.
  • Retrying immediately. Without a pause the retry lands on the same limit and only extends the refusals.

A pool for Wildberries monitoring

Rotating IPv4 from 1375 ₽ for 100 threads, traffic not metered. The rotation mode is switched in the dashboard.

View pricing

Proxies for this job

Check it with our tools