Yeah thats a super tight ETA, I like to be accurate.
Have you tried things like reverse proxies back connect proxies (change the ip on the back end every 10 mins, I think they are private proxies) or there is also proxy rack, which just changes the ip on every request. I use proxy rack and its pretty impressive. Its slow, and public proxy based I believe, but it works well for the things I use it for and I have the 200 connection pack and its still faster then using filtered public proxies because they do all the work on the back end.
Also there is solid proxies or something like that, they are newer, and they utilize an api where you can request a new proxy. So they give you a fixed IP just like reverse and proxy rack, but then when the ip becomes blocked by google/search engine/site your using it with, you can programmatically request that the ip be changed on the back end. Its a nice mix, because proxy rack changes it on every call and reverse changes it every 10 mins but with the solid solution (or whatever its called, can't remember) its changed on demand based on when you want it. So you could specify based on X error request a new proxy.
Thats not integrated with Scrapebox, but you could build your own api tool that just requests a new ip every X often based on your experience of when you need it. Anyway, just tossing it out there, might save you some cash with some of those.
When the automator comes out in 2.0 I plan to build my own automator file that runs that grabs proxies from my own custom sources and filters and kicks them out to a file every X mins that I can then share out to my servers via dropbox. Maybe anyway, I just got done implementing a completely automated scrape and filter setup between multiple servers and its running great with paid stuff so not sure I will need it. Its an option anyway.
