Amplify
New member
so after my last post about scaling i figured id tighten my geo-targeting, get better localized content for a project. saw a thread somewhere with a 'deal' for geo-targeted residentials, price was too good to be true but i was tired of paying like $15 per gb for solid ips. vendor promised city-level targeting for like 5 bucks a gig. set it up for a news aggregation scrape across 3 european cities. first 100 requests were golden, ips looked local, response times decent. then the cr started dropping hard. like from 90% success to maybe 40% after a few hours. checked the logs. the ips were supposedly from frankfurt but half the requests were getting routed through datacenters in freaking miami. the geo-db lookup i run on the side confirmed it. they were selling me a backconnect pool with bad routing labels. wasted a day's work and the data is useless cause the localized ads and content are all wrong. moral of the story? if a geo-proxy deal seems cheap, they're prob just slapping a location tag on a random ip pool and calling it a day. ask for a small test batch first. always verify with an external api like ipinfo or maxmind on a sample of the ips. i learned the hard way again. anyone else got burned on a 'localized' proxy promise lately?