08-27-2014, 04:23 PM
I've been using Buy Proxies for the last 2 days (in Loopline's link above) and they've been great. I bought 30 shared proxies. There was a little hiccup with my first set and they died after 1 hour and they said it was because I was using too many keywords (which I disagree). I was only using 1 connection with 30 IPs. They supplied me with a fresh list of 30 and I've been scraping today for the past 5 hours (about 78,000 results so far) without interruption.
Their customer service responded in minutes! It was awesome. In case you're curious about the issue I had, then continue reading. The information might be helpful for you in the future. Loopline can correct any assumptions that I might have wrong.
The issue might have been my fault, I was using the single-thread harvester, and I think it might have been cycling through the IPs in sequential order, and Google might have caught on. They were non-sequential IPs, but some were really close in sequence. Pair that up with similar looking searches across close IPs and they can put 2 and 2 together I'd imagine.
Anyways, what I did to fix this was used the multi-threaded harvester with only 1 connection with the new IPs and it is chugging along perfectly. I'm guessing that the multi-threaded chooses the IP to use at random. My first assumption for the issue was that Buy Proxies might have paired me up with a more aggressive user and they got the proxies banned, but they tried to indicate that it was my fault. I'm not so perfect that I can't screw up which is why I came up with my alternate theory above.
Their customer service responded in minutes! It was awesome. In case you're curious about the issue I had, then continue reading. The information might be helpful for you in the future. Loopline can correct any assumptions that I might have wrong.
The issue might have been my fault, I was using the single-thread harvester, and I think it might have been cycling through the IPs in sequential order, and Google might have caught on. They were non-sequential IPs, but some were really close in sequence. Pair that up with similar looking searches across close IPs and they can put 2 and 2 together I'd imagine.
Anyways, what I did to fix this was used the multi-threaded harvester with only 1 connection with the new IPs and it is chugging along perfectly. I'm guessing that the multi-threaded chooses the IP to use at random. My first assumption for the issue was that Buy Proxies might have paired me up with a more aggressive user and they got the proxies banned, but they tried to indicate that it was my fault. I'm not so perfect that I can't screw up which is why I came up with my alternate theory above.