Proxy field notes Response codes Pool sizing Choosing an address

Proxy field notes

Notes from running address pools and collection jobs: a code reference, the pool sizing formula, address criteria per task, and longer pieces on the problems that come up most often.

Reference

• Response codes when working through a proxy: what each code means, which layer issued it, what to do next.
• Sizing an address pool: how many addresses a job needs given its volume and window.
• Choosing an address by task: why data collection and account work pull in opposite directions.

Articles

• How to test a proxy before you rely on it: the probes that catch dead addresses
• Proxy speed test: how to measure every stage of a request and find what actually moves it
• SOCKS5 proxy, HTTP or HTTPS: picking the protocol by what breaks first
• Shadow ban check: the account is alive and nobody sees it

Who this is for

People who scrape marketplaces, run several working accounts, or launch scheduled jobs. Tables, formulas and the order of checks, with the preamble skipped.

The addresses behind these notes come from a private pool with no neighbours in the subnet, because every calculation here holds only while the allowance of an address belongs to you alone.