Akamai Bot Manager: passes home IP, fails through residential proxies

Wait 5 sec.

I read public product pages (price and per-size stock) from two retail sites behind Akamai Bot Manager: a few pages per brand every few hours, no login. Site A works from my home connection but not through proxies. Site B fails everywhere. Site A Setup Passes Patched-Chromium anti-detect browser, headless, my home ISP line 10/10 Same browser, residential proxy, rotating IP 1/10 Same browser, residential proxy, sticky session 2/10 Same browser, sticky session, gateway nearer the country 5/10 playwright-extra + stealth, headless, same sticky proxy 0/10 Free datacenter proxies 403 every time All exit IPs were Thai carrier ranges. Failures show Akamai's "unable to give you access" page with a reference code, or a page loaded without the availability XHR. Plain curl gets a timeout or a ~3.4 KB 403. Site B: "Access Denied" (title "Access Denied") from every route: home IP, residential proxies, four different anti-detect or stealth browsers. One got through 3/10, then 0/10 on fresh profiles. My stealth setup, in case I'm misusing it: chromium.use(require('puppeteer-extra-plugin-stealth')()); const browser = await chromium.launch({ headless: true, proxy }); const ctx = await browser.newContext({ userAgent: UA, locale: 'th-TH', timezoneId: 'Asia/Bangkok' }); Questions Is Akamai's decision mostly fingerprint or IP reputation? The same proxy gave 5/10 with one browser and 0/10 with another. Do static ISP IPs do better than rotating pools for repeated reads of one site? Has anyone got a site like B loading reliably, headless or only headed? Is a small always-on worker on a home connection the usual answer?   submitted by   /u/AKSB_TG [link]   [comments]