proxies getting banned faster on google

[mazgalici]

I saw that google is more aggressive with the bans in the last period. I'm paranoid or you saw it too?

 

[ponasjulius]

Well you should use private proxies instead. Public ones usually get banned fast. However, getting "google clean" proxy is hard these days... :/

 

[kappa84]

lol mazgalici is offering proxies so he talks from experience

and yes mate, they are getting banned faster indeed, it sucks!

 

[proxygo]

ive been port scanning public proxies for 6 yrs.
3yrs on bhw. and i can still get aprox 3k google
passed proxies a day to support 600 subs on my
service. my point ?

Well you should use private proxies instead. Public ones usually get banned fast.

public scraped proxies suck, because everyone else can scrape the same
proxies = why the get banned so fast because your all using proxies from the same pool
port scanning public proxies is searching out piles of unlisted public proxies
that google isnt tracking. if it didnt work, explain on a service of 600+ users
using public proxies i port scan - ive never done a single refund on bhw since
i came here in 2008.. and thats because its all about your sources .

ille put this another way..go grab 5k public forum listed proxies and test them.
you might get 500 or so google passed...test them again in about 2/3 hrs
most will be dead, because the same proxies you scraped tested and used,
others are doing it with the same proxies, any list you can scrape, anyone else can
which is why the die and get banned so quick.

i can post to my 600 subs a list of port scanned public of say 1.5k google passed,
and 10 hrs later 3/400 will still be live..why ? you cant scrape port scanned public proxies.
so port scanned public proxies will out last public url scraped proxies 3/1 everytime
everyday...FACT.

 

[MyOtherPersona]

I saw that google is more aggressive with the bans in the last period. I'm paranoid or you saw it too?

Yes, there is a major change. We were detected about 1 time out of 1000 requests before. Now, since yesterday morning, the detection is more like 1 out of 2.

It affects lots of proxy providers. I even got an email from one of our proxy providers today

A number of users have been reporting a higher than normal rate of 403 errors from google. 403 error means google thinks you are a bot. This is a normal error to receive but lately our proxies are receiving it much more often. This issue is widespread across our IPs. We are aware of it and taking measures to try to fix it. Please trust that we are doing the best we can (ordering new servers and IPs takes time).

It seems that recently Google increased its enforcement of scraping and they changed the limits some how. So behavior that did not previously cause problems is causing individual IP addresses, sometimes entire blocks of IP addresses, to be banned. It may be wise to cut down your rate of scraping and increase the velocity with which you switch IPs. It may also be worth it to ping Scrapebox support about this and ask them to change the request rates.

Unfortunately, this problem has affected multiple proxy providers so it definitely seems like a change that google made. We are doing as much as we can on our end: we are working to decrease the number of users per proxy, limit overuse by individual users, and increase speed.

Until then, thank you very much for your patience. Please rest assured we are aware of the issue and working on it.

Any ideas about new request patterns that reduce detection?

 

[raton]

I'm working with "YoTub" and I only use private proxies from different providers, and they started to ban some of my accounts. At first I thought it was the accounts but after I've used a different ones same thing happened. Then I've found a pattern, when I was using the proxies and I reached the 4th IP from the same class all the accounts were banned, if I only use 3 IP's from the same ip class the accounts are ok. Did anyone else experienced this ?

 

[xrnew]

Exacly, I saw it as well.

 

[dracony2]

are you by change using inurl in your queries? The rate depends on the keyword you are scraping. Sometimes my prooxies get me nothing in scrpebox, so i change the keyword and voila, it works

 

[portalweb]

I notice it too (more 403 error messages) from my specialized SEO tools as well as the public proxies. It means we need to spread out the proxies (private/public) more often to minimize the 403 error issue.

 

[proxygo]

I notice it too (more 403 error messages) from my specialized SEO tools as well as the public proxies.

no problems here still getting the same amount of Google passed proxies
i always get. 1k in a morning - 1.5k in the evening, no change here

 

[portalweb]

no problems here still getting the same amount of Google passed proxies
i always get. 1k in a morning - 1.5k in the evening, no change here

Same here with Proxylist.co/Webproxylist.com related to Google proxies - not an issue. Remember, Testing and using proxies are different. Testing is nothing. How we are using proxies is the major issue we are having right now.

The real issue we are having RIGHT NOW is that Google is banning IPs much quicker than before as stated by OP, which I saw it from the testing we have with my specialized tools.

We are studying on finding the ways to get around the Google 403 error ban by experimenting with different access methods via user agents, referrers, frequent timed IP rotations, etc.

Until then, the proxy users will need much more proxies (10-100x more) in order to access to Google. It means more $$ for users to shell out to proxy providers.

 

[mazgalici]

no problems here still getting the same amount of Google passed proxies
i always get. 1k in a morning - 1.5k in the evening, no change here

that is normal because your proxies are new but when the users will start to perform searches they will have the same problem

 

[proxygo]

also maybe consider of mixing things up a little maybe try getting socks proxies
as well for scrapebox as well as HTTP, there less used. did a little test on that
this morning ....even without port scanning - because i dont port scan socks,
only HTTP proxies , i was able to throw in and get working without really trying
around 200 socks proxies working on scrapebox, aprox 190 where anonymous
and around 50 Google passed ..

 

[portalweb]

because i dont port scan socks,
only HTTP proxies , i was able to throw in and get working without really trying
around 200 socks proxies working on scrapebox, aprox 190 where anonymous
and around 50 Google passed ..

We are talking about the use of proxies for Google access, not how the proxies are tested.

I and my other two developers are running the Google access tests (private and public proxies) to find the best solutions...and will post the results here shortly.

 

[clfox]

Since last week Google has been monitoring aggressively for proxy scrapping .. You certainly will need lot more subnets + IPs in order to scrape here on...

 

[proxygo]

well since i provide proxies to 600+ users of bhw
from donors/vips/excs/3 mods, not 1 person has contacted
me and said there results have fallen or the length of time the
proxies last for has fallen .. so nothing to report here..
i am sorry to see your having a few issues with google with your
proxies and i hope you can resolve it, but as of yet, until any of
my subs say otherwise i can only assume everything is ok

but to find out i posted a message to my subs and ille let you no
what they say, as my service is also targeted for scraping . ille
let you no what they say..

[3:02:41 PM] tony: quick question guys, i see a few proxy sellers on bhw
saying that Google is becoming more aggressive blocking there proxies
they provide for users to scrape with, can anyone confirm if the proxies
i am providing are working better/worse or is everything working the same as usual..

 

[blackamp]

"proxygo"
I have been reading multiple explanations on your behalf and I believe you lol, port scanning to further find ports. I have been wasting so much time on finding proxies than on my url research lol. I would absolutely purchase your service and use NiX but hell, can't afford a single domain as of yet :/
Soon though
About Google banning, I did notice something, yes. Forum posted scrapes from fellow members also appear to drain like lightning quick too. Proxies are the bases of SEO research.

 

[silentthunder]

that is normal because your proxies are new but when the users will start to perform searches they will have the same problem

I agree 100%. It's completely different on the user's end and I've been noticing new private proxies being banned much faster for two months now.

 

[NIXMY]

"proxygo"
I have been reading multiple explanations on your behalf and I believe you lol, port scanning to further find ports. I have been wasting so much time on finding proxies than on my url research lol. I would absolutely purchase your service and use NiX but hell, can't afford a single domain as of yet :/
Soon though
About Google banning, I did notice something, yes. Forum posted scrapes from fellow members also appear to drain like lightning quick too. Proxies are the bases of SEO research.

I can hear you. Automation is your key to success. I also used to do everything manually before 2010. 2 years automation, I've saved maybe million years of my time.

To me it seems this issue affects mainly to private proxy providers.

 

[SEOnetic]

I have been getting like 40% success from my custom lists before it was 60%. But they do work for a few hours now.