Do you think dedicated proxies are actually dedicated?

gman777

Power Member
Joined
Apr 7, 2016
Messages
715
Reaction score
676
I remember a couple months ago that I've bought just one dedicated proxy from some BHW's provider. I wasn't using it for a couple days, yet when I wanted to access it: BOOM! 302 error in Scrapebox.

How can a dedicated proxy fail if it was allocated only to me? Which leads to the question: what if dedicated is just a marketing gimmick?
 
You bought one proxy.

Proxies are not special, if you are heavy handed with them (and it's easy to do this in scrapebox) they will get blocked just like a regular IP.

I would only buy one if it was for a social account or whatever. For scraping you need a lot, sock proxies that rotate are better for this.
 
Do you think the girl just met is virgin?
No, man. I'm saying that I've bought a dedicated proxy. Proxy was working fine when I first tested it. Then I left it away for a couple days without using it. And when I tried to use it, it didn't work. Does Google ban a proxy that hasn't been used?

I didn't say virgin, I've said dedicated. I know that proxies fail a lot in Google. But, anyway, that was maybe just my impression. Probably it was an illusion.

Anyway, @I know SEO can you please close this thread?
 
I use public proxies for scraping and run gsa on native IP
 
Does Google ban a proxy that hasn't been used?
Yep, google is kind of banning/flagging proxies by range so if alot of proxies were abused from IP range where you have proxies you may have problems with scrapebox.
Also scrapebox behave in different way than normal user and google see it. Often proxies dont work in SB but work via browser, advanced russian scrapers work via real browser to get more results per proxy. Your problem dont mean your private proxy is shared.

One more thing, i just took one proxy and harvested a ton to ban it in google, banned proxy give 503 error, not 302.
 
It can fail pretty easy, I've run some tests with google and proxy provider allocated to me /24 same range of proxies. I've split them at ~50 per group and started testing. Then I've got them banned and moved to other group, to my surprise all proxies were burned. They were allocated to me only. Once when I burned them they stopped working. Entire range /24 was burned (sending captchas).

So, if you got dedicated proxy .234 and someone is using same proxies from that group like .10-125 (just randomly said) and get them burned, from what I've noticed, entire /24 goes on temp ban. I know it sounds crazy. I've tested it couple of times and that's what happened. Approx 6 months ago.
 
It can fail pretty easy, I've run some tests with google and proxy provider allocated to me /24 same range of proxies. I've split them at ~50 per group and started testing. Then I've got them banned and moved to other group, to my surprise all proxies were burned. They were allocated to me only. Once when I burned them they stopped working. Entire range /24 was burned (sending captchas).

So, if you got dedicated proxy .234 and someone is using same proxies from that group like .10-125 (just randomly said) and get them burned, from what I've noticed, entire /24 goes on temp ban. I know it sounds crazy. I've tested it couple of times and that's what happened. Approx 6 months ago.

Actually it makes sense. If you're Google, you've got tons of historic data. You simply run a report of which IPs were blocked recently and determine it's all a C block of IPs. a.b.c.XXX all XXX are burned frequently. Google then places a tighter tripwire for a.b.c.... That's what any of us would do, why wouldn't Google.

So even if the proxy is dedicated today, it may have been burned 3 months ago by a previous customer. Google already knows that IP block is for proxies.
 
Back
Top