serpfetcher

Every number on this page is a FLEET total across all 10 exit boxes, unless the row below says per IP.

The five tiles up top — fleet totals
up now	Exit boxes that can serve a query this second	out of 10
resting	Exit boxes Google has banned, sitting out their penalty	want this at 0
spare hits	Queries the whole fleet can still run this hour	500 when untouched
wins today	Searches that came back with results	lifetime, not today
bad runs	Searches where every exit failed	lifetime

Limit	Per IP	All 10 IPs
Queries per hour	50	500
Queries per day	800	8,000
Gap between queries	72s (jitter ±30%)	~7.2s

Why so slow: live testing showed a single IP hard-bans at 72 to 112 queries whatever the pace, and firing in bursts triggers it fastest. The 72 second gap spreads the hourly allowance evenly so no box ever bursts.

What each exit box status means
ready	Free to serve right now
pacing	Healthy, just waiting out its 72 second gap. Normal.
spent	Used its hourly or daily allowance. Comes back on its own.
resting	Google refused it. Parked, and deliberately not probed.
down	The worker process is unreachable. Needs a look.

Exit box status columns — these ARE per IP
exit ip	The public IP that query leaves from
this hour	Used against that box's 50 per hour
today	Used against that box's 800 per day
next slot	Seconds until that box may fire again
served	Successful fetches from that box
banned	Times Google refused that box
resting	Minutes left on that box's penalty

The meta block in every JSON payload
exit_ip	Which of the 10 boxes actually served it
cached	true means it came from the 24 hour cache, no Google hit, no allowance spent
elapsed	Server side seconds
bytes	Raw Google page size, normally about 4 KB
attempts	Every exit tried and why it was skipped, in order

Status values in the payload
ok	Results returned
empty	Google answered normally but nothing parsed. No IP was punished.
blocked	Google refused that box. It is now resting.
exhausted	Every exit was resting, spent or pacing. Try again shortly.