Proxies for A-Parser
Private addresses for multi-threaded data collection in A-Parser.
Proxy plans for A-Parser
Every plan includes both IPv4 and SOCKS5.
Threads are simultaneous connections. The more threads, the higher the parallel load your software can handle.
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 1,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 1,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 1,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 1,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 3,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 3,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 3,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 3,000 threads
Proxy catalog for your task
Why A-Parser needs proxies
A-Parser is a multi-threaded scraper that can run hundreds of threads at once. When all threads run from one address, sites respond with captchas and slow you down.
A-Parser is built for volume: it can store a proxy list, check it and assign proxies to jobs on its own. What matters most is where the program gets the list from and how often it reloads it.
What to know about proxies for A-Parser
A-Parser sends thousands of queries over several hundred threads, and from a single IP it quickly runs into captchas and rate limits. That is why you need a rotating pool: each thread or batch of queries gets its own IP.
You get private IPv4 over HTTP, HTTPS or SOCKS5, as IP:PORT bound to your IP or as IP:PORT:LOGIN:PASS. Load the list by link: it refreshes every 15 minutes, and the program can reload it on a schedule.
What proxies you need for A-Parser
| Protocol | HTTP, HTTPS or SOCKS5 |
|---|---|
| List source | a link or a file from your dashboard |
| List refresh | every 15 minutes |
| What to count | threads in the job |
| Online | 12,000-15,000 IPs online daily |
| Authorization | by binding your own IP in settings, up to 2 addresses |
How to load a proxy list into A-Parser
A file works too, but then you have to refresh it yourself.
The number of addresses depends on how many threads the job runs at once. With fifty threads on ten addresses, each address carries five times the request rate and hits limits before the job is half done. The thread limit comes with the package and does not stack across packages.
Related settings are covered on the page about data collection.
- Match addresses to job threads
- Each package has its own thread limit, so to scale up you need a bigger package
- Choose the format by how many machines run the jobs
How to connect proxies in A-Parser
To start, bind your IP in the settings, meaning the server or home computer where your proxy software runs. Without it, there is no connection. Two formats are available: the standard IP:PORT and IP:PORT:LOGIN:PASS for software with login and password fields.
In A-Parser, proxies go in the Proxy Checker section or straight into the task preset: paste the list one address per line in IP:PORT format and set the type to HTTP or SOCKS5. A-Parser spreads them across threads on its own.
Before a big run, check the list with the built-in Proxy Checker. The free test shows how many addresses your thread count needs before you buy.
How to buy proxies for A-Parser
The process is simple. Sign up in the dashboard, request a free test of up to 2 hours, bind your IP and open a ticket with the operator to try A-Parser on your own tasks.
If everything works, choose a package by thread count and term, pay in crypto, and access opens right after payment. You can take the free test once, before you buy. If you have questions, open a ticket.
FAQ
Will these proxies work with A-Parser?
A-Parser accepts HTTP, HTTPS and SOCKS5 proxies in IP:PORT format, which is the format we provide. The free test shows exactly what your thread count needs.
How many threads can the pool handle?
The pool of 12,000-15,000 IPv4 gives each thread a different address; how many threads run at once depends on the package.
Which protocol should I choose?
HTTP and SOCKS5 both work for most A-Parser tasks; SOCKS5 is handier for non-standard connections. You can check both during the free test.
See also: proxies for Screaming Frog, proxies for Netpeak Spider, proxies for Key Collector, proxies for scraping, proxies for price monitoring, proxies for SEO, HTTP and HTTPS proxies, proxies for anti-captcha and checkers, full catalog
© WinGate · source of the material · wingate.me/en/proxy/a-parser-proxy