Recent Scrapebox Proxy Issue, everyone should note

I notice the drop in working proxies too.

Based on Proxylist.co's today internal stats, I see around 2,500-3,000 working SB/G00gle proxies available at a given time (updated every 15 mins around the clock), down from around 4,000-6,000+ SB/G00gle proxies as part of Worldwide proxy package. (Note: SB/G00gle proxies are different from other Proxylist.co's multi-proxies pakcages).

I think things will come back to normal in few weeks...who knows?
 
can only be 2 factors
1 - public proxies have fallen really badly
2 - theres a problem with the proxie tester

I think proxygo that a little of both reasons but main is still nr 1. It seems to me also that the reasons for the falling number of public proxy, refer to the growing number of people using them.

I notice the drop in working proxies too.
(...)
I think things will come back to normal in few weeks...who knows?

The specificity of public proxy does not allow us to stay left with nothing. Public proxy will always be. Only increase the demand for good public proxy, which I think could be even better than private.

A large amount of public good proxy is better than any number of private, and mainly due to the following reasons:
- they are much cheaper
- so that there are a lot more, when one is banned by Google, you can easily replace with new
- parameters of the good public proxy are not at all worse than the private proxies, and often even better
 
and as public proxies are failing scrapebox test either
due to the drop in numbers or tester problem
im finding the only way to get any decent amount of
public proxies is to port scan them. down side is its time
consuming
 
Thanks for the information. Please keep us informed what is going on. With what can we check proxies except Scrapebox build in proxy checker ?
 
UPDATE

Scrapebox support got back in touch and told me that their only solution is to stop using g89gle altogether in SB.

LOL

They think this issue is happening because their was an update to how g89gle handles requests. But my php proxy checker still works fine, so if it's true then it must be how SB is sending the requests in comparison to a php script.
 
UPDATE

Scrapebox support got back in touch and told me that their only solution is to stop using g89gle altogether in SB.

LOL

They think this issue is happening because their was an update to how g89gle handles requests. But my php proxy checker still works fine, so if it's true then it must be how SB is sending the requests in comparison to a php script.

You can do a packetlog and see exactly how SB is sending the requests. ;)
 
wow i tested 49k unique proxys today
30k port scanned 20k scraped
3.5k passed bleach
300 went through scrape box wtf
 
what was the date of the update
for the proxy checker.?

is this update new today
v1.15.32
 
Last edited:
I only use sb for posting and a different software for scraping, so i never have any problem:)
 
You can do a packetlog and see exactly how SB is sending the requests. ;)

Honestly, I don't have time for investigating it. It's easier to just stop using SB for these tools and hope that they fix it, using my own php scrapers and testers instead in the meantime.

I was more concerned for my customers and the community.
 
I need to scrape 60k links everyday, now what?? Is SB down for good, this update didn't fix anything!!
 
scrapebox isnt down let me repeat it isnt down
u can still scrape google yahoo aol
its the proxies that are down to do the job
or a problem with s/box or a google update
u can still scrape with scrapebox you just
need the proxies
 
scrapebox isnt down let me repeat it isnt down
u can still scrape google yahoo aol
its the proxies that are down to do the job
or a problem with s/box or a google update
u can still scrape with scrapebox you just
need the proxies

Actually no, the proxies are fine. I test them through php cURL proxy checkers, I test them through FireFox and I can connect to G00gle fine, but when I test with SB they don't work. Then other people report the same thing to me. That is clearly a scrapebox issue.

I did see an update and the issue seemed to improve, but there are still lots of proxies that don't work in SB but work fine other ways. I told SB about this and they didn't respond.
 
and ille repeat the amount of public proxies
available passing Google has fallen this happens all the
time..proxies amounts go up and down..when public proxies
fall like they have done for a a few weeks there's less proxies
to pass Google..that's obvious
 
Last edited:
and ille repeat the amount of public proxies
available passing Google has fallen this happens all the
time..proxies amounts go up and down..when public proxies
fall like they have done for a a few weeks there's less proxies
to pass Google..that's obvious

That is not the point. Regardless of the amount of good proxies that are available, I have a ton of working proxies that I can use with other software and use manually through a browser, but they are failing with SB.

So yes, SB has a problem. The point of SB is to be able to scrape with my proxies that work, but they are not working with SB for some reason. Blaming the number of proxies available doesn't solve the problem. So now I am not using SB to scrape anymore cuz it's slowing me down too much.
 
then let me ask you this even with your tools
scripts how many proxies do u get passing google
against how many passed in scrape box..ille hold
of my answer till i get a reply..
 
Back
Top