Proxies
One egress per line. Saving replaces the whole pool and restarts the monitor.
In pool
255
saved proxies
Healthy
255
answering right now
Benched
0
cooling down after failures
Pool
host:port:user:pass
Each event holds one proxy for as long as its session lives — tickets.com binds its cookies to
the egress IP, so a session that changes IP mid-flight gets challenged. More proxies means more
events can run with an egress of their own.
Mint pool
residential only
16 tokens ready
Kept separate from the pool above, and it has to be residential. reCAPTCHA scores
ISP ranges below the threshold no matter what else is done — measured 0 accepted out of
every ISP attempt, against roughly one in three on residential, and better than that once
the browsers have been parked a while. The pool above is fine for inventory polling and is
cheaper, so only minting draws on these.
A token is bound to the site key, hostname and action — not to the event — so one parked browser serves every event you watch. Bandwidth does not grow as you add events.
A token is bound to the site key, hostname and action — not to the event — so one parked browser serves every event you watch. Bandwidth does not grow as you add events.
Ready
16
of 16 target
Minted
602
this run
Failed
18
mint attempts
Spent
0
586 expired unused
Browsers
80
parked so far
Per token
0.8s
avg on a parked browser · last 0.5s
Browser start
17s
launch + page + dwell, once per browser