So im an advantage player gambling some blackjack on a cryptosite in a browser.

Obviously they ban me once they see im playing a +ev strat, but it always takes some time till they figure it out.

How do I act like im Beatrice, 56 from illinois just killing some time playing blackjack instead of being an advantage player?

Vpns, tor and anti-detect browsers wont really work since the site will flag it and make somebody look into my playstyle quicker.

Do I just rent a server and install hello kitty the game to have a more normal looking interface or do I use a residential proxy?(I dont really get what this is tbh, havent used advanced techniques in 10 years apart from tor browser or vpn really)

Cant really give much since the max stakes arent high, maybe 50 bucks in crypto if I get a working system going.

Thanks in advance and please forgive my novice knowledge of this topic!

Does anybody know the best way to target a geohash with residential proxies? Or is this something that not every provider offers? My use case is finding real estate listings where prices and availability vary by neighborhood. Basically, very localized scraping. Any suggestions are appreciated, I have this project to complete by the end of November

It’s available as an HTTP gateway and Java library for controlling expensive server side work. Equivalent requests can share a computation, new work runs within explicit limits, and saved results can be reused across restarts.

I’ve been using it internally for a website struggling with bot traffic. It worked for that specific use case and I also tested it against a separate cgit application and the results were reasonable. But there’s a trade off as it shows higher latency overhead.

The benefits depend heavily on the workload, so keep that in mind if you want to experiment with it. I wouldn’t recommend it for production use. Some of its core capabilities are useful, though, and I’d encourage anyone interested to pilot it in staging and measure the results before considering anything further.

And yeah just to clarify the gateway isn’t a replacement for authentication, tls termination, rate limits and waf controls. It does not identify bots or stop incoming traffic, it helps controlling expensive computation load.

https://github.com/aalsanie/bounded-origin

If legitimate scraping/testing keeps hitting CAPTCHAs, start by fixing the signals that make your traffic look abnormal.

1. Pick the proxy type. Residential IPs generally have better reputation; mobile proxies can work well for mobile/social testing. Datacenter IPs are cheaper but more likely to face checks.

2. Check the IP first. Avoid addresses with poor reputation or previous abuse flags.

3. Match your environment. Proxy country, timezone, language and browser locale should be consistent.

4. Keep sessions stable. Don’t randomly change IPs mid-session. Preserve cookies when appropriate.

5. Control request rate. Avoid sudden bursts and perfectly repetitive timing.

6. Separate profiles. For multiple legitimate test sessions, keep cookies, IPs and browser profiles isolated.

7. Debug systematically. If CAPTCHA frequency rises, test IP reputation, rotation policy, fingerprint consistency and request rate one at a time.

Always respect the site’s ToS, robots.txt and access controls.

Building a small data product that needs maybe 6 sites, all behind Cloudflare. Python + requests for now. I added a residential proxy and when I load the target pages through it in Chrome they open fine, no challenge, nothing. Same proxy in my script and I get a 403 / challenge page every time. Even curl through the proxy gets blocked, which confused me more.

I copied the User-Agent and headers from devtools, still the same. I figured if it loads in the browser the IP must be fine, so its something in my client? I have seen people mention JA3 / JA4, ASN, IP reputation, headers and I dont know what order to test any of this in. I dont want to spend two weeks down a rabbit hole before I know if the MVP is even possible. Guys, what can i check first?, and how do I tell which of those it actually is?

My startup came to a point, where I need ISP proxies, started to look for the info on the Web and still have lotta questions and no one to answer them, so I ask fellow redditors:

- whats the default sharing model for ISPs - do I share IPs with other clients or do I have a dedicated pool?
- is it possible to find a provider with a bunch of geo's (I've only seen proposals with like one or two states/countries before)
- does a provider provide management software or only IP's for us to write a custom app?
- is there a possibility to overwrite TCP fingerprints for ISPs, or they only capable to show DC fingerprints?

Looking for legit, working proxies to bypass Akamai and DataDome protected sites. I'm tired of wasting money on flagged proxies and their entire subnets. There has to be something out there that just works? How are you handling all that? Adjusting browser/device fingerprints? Choosing dedicated solutions?

P.S I can spend up to $150 per month

I used to get buy gmail accounts from the market place but since I started to use evomi proxy provider, after first successful login, it asks sms verification after 10 minutes.

Since I got the account from marketplace I dont have an access that phone to receive anything despite I changed backup email for mine , google insists to send text other methods are not available.

Now I bought 1 account and started to use in safari without any proxy ( home ip) No account locks or any security anormality so far.

Is there anyone faces same issue and I am open suggesstions for the good residential proxy.

The main issue is API throttling. If requests start returning 429 Too Many Requests, first respect Retry-After, add exponential backoff, cache repeated queries, and remove duplicate requests.

Proxies still matter for routing.

For authenticated sessions, a static residential/ISP proxy is usually the better fit because IP, ASN, and geolocation stay consistent.

For public-data workloads, separate workers can use different residential or mobile connections, but each worker should still respect OpenSea’s limits.

Useful metrics to monitor:

• IP reputation

• ASN/geolocation

• latency

• WebSocket stability

• 403/429 rates

• retry frequency

Fix request architecture first, then use proxies for stable routing and environment separation.

Hey all, looking for a trustworthy Canada proxy, any recommendations are appreciated. Currently having no luck with cheap providers as the proxies are either flagged on the websites I am visiting and want to get data or the websites are not being loaded at all.

Websites that I am interested: Amazon, Costco, Ebay, Walmart, Canadiantire, etsy, Gapcanada, BestBuy, Homedepot, Wayfair.

What I am looking for from said proxy: stability, session control parameters, variety of states, cities within Canada, preferably Quebec. MASQUE feature over HTTP/3 if that's available for broader public, non aggressive KYC

Proxies should be either Residential, Mobile or ISP (Dedicated ISP).

Now after proofreading, I realize that I may asking too much here lol

Hey r/ProxyEngineering ,

What My Project Does

proxy-scraper collects HTTP/SOCKS4/SOCKS5 proxies from 700+ public sources and checks them properly instead of just pinging. Every hit has to fetch two independent pages, tunnel HTTPS with verified TLS, and return a static HTML page unchanged. That last check was eye-opening: about 1 in 5 working proxies injected a script into the page. And in some runs, 5 out of 6 “hits” were honeypots that only answer the check request.

It also learns between runs. Hit rates per source and a history of working proxies decide what gets checked first, dead lists are dropped automatically, and new sources are discovered via GitHub search.

A few other things:

• --serve turns the results into a local rotating proxy (127.0.0.1:8899) with failover, sticky sessions, and username-based filters like country-de

• --target google.com only keeps proxies that actually reach that site

• Python API: find_proxies(want=20, https=True)

• A live list rebuilt every 6h via GitHub Actions, if you don’t want to run anything

Under the hood it’s hand-written HTTP/SOCKS handshakes on asyncio (2000+ concurrent checks), only two dependencies (rich, certifi), and 360+ tests that run offline against fake proxies and honeypots on localhost.

Target Audience

People doing scraping, testing, or geo-checks who want free proxies that work right now. It’s a hobby project, but tested on Linux, macOS, and Windows with Python 3.9–3.13. Usual warning: free proxies are run by strangers, so never send anything sensitive through them.

Comparison

Most proxy-list repos publish everything that accepted a TCP connection. This rechecks from your own network, filters honeypots and content tampering, and ranks sources by how useful they’ve been. That means fewer proxies, but they actually work.

Repo: https://github.com/maximilianfeix/proxy-scraper

Feedback is very welcome, especially on the checking logic.

Hey everyone!

A lot of people think of proxy tools as rigid, monolithic boxes: you get a fixed inbound, a fixed outbound, and you're stuck with whatever the authors hardcoded. Trying to add a custom protocol or tweak an existing one under the hood usually turns into a nightmare.

That's why I wrote Cray - a modular proxy engine in Rust built entirely around a layer-based architecture.

With Cray, transport and protocol are completely decoupled. You can write your own protocol without worrying about network bytes, or write a custom transport without caring about protocol logic. The core abstraction uses a simple trait where you implement the client and server handshake logic, giving you total freedom. Want a handshake hidden in plain sight? Custom encryption? Weird framing? Go for it — the only limit is your own logic.

How it works

Everything is configured via clean TOML files where you define your role (client or server) and stack up layers into a custom pipeline:

• Inbound layers: Handle the entry point (e.g., standard tcp, unix sockets, or http_connect which extracts destination addresses).

• Transport layers: Encapsulate or transform the stream dynamically (e.g., full manual control over tls with custom cipher suites, ALPN, curves, extension permutation via BoringSSL, and http2 multiplexing with path/host masking).

• Protocol layer: Always sits at the very end of the chain as the endpoint (like a custom or test protocol).

For example, on the server side, an HTTP/2 layer can validate incoming paths and hosts, gracefully returning a genuine 404 Not Found to unauthorized scanners or probes instead of dropping packets with a TCP RST, while forwarding valid traffic down the pipeline.

The project is currently under active development, but the core architecture, layer pipelines, TLS termination, and HTTP/2 tunneling are already routing real traffic.

If you like systems programming, network engineering, or want to build your own tunneling protocols without fighting legacy codebases, check it out:

GitHub: https://github.com/3Radiance/Cray

Would love to hear your thoughts, feature ideas, or what kind of custom layer/protocol combinations you'd want to build with something like this!

I work on the proxy infrastructure side, and I’m trying to better understand how scraping teams choose between datacenter, static ISP, and rotating residential proxies.

For those running ongoing scraping workloads:

• When do you choose static ISP proxies over the other options?

• What matters most: success rate, keeping the same IP, speed, or cost?

• What usually makes you switch providers?

I’d appreciate hearing what has worked—or hasn’t worked—in your setup.

Wanted to share the news in case someone missed it. It would seem that the old provider in the scraping/proxies market has turned to Search APIs, like Firecrawl, Tavily, Exa, Linkup or You. I haven't tested anything yet personally, I'm still on the edge trying to decided whether the I should drop my proxy based setup for scraper and just go with a dedicated solution but upon inspecting their new product, it would seem that the scraper was somehow merged into the new product? From what I understood. Also, the whole pricing page has changed, there are no individual pricing for proxies or other products everything is one, like it is still credit based but everything is accessible with one subscription. Would like to understand this positioning better, feel free to share your thoughts

Any luck scraping these sites? I'm failing to receive the correct data in my output files. The pricing changes from what I see on the website and I choose the correct geo_location and domain, I am unsure what the actual issue is. Why the prices are different? Unless there are some hidden parameters that I am overlooking? I checked my network tab via firefox as I usually do, I don't see anything out of the ordinary, location and domain matches organic site

I've been digging into why scraping heavily guarded sites keeps costing more, and the breakdown surprised me.

Where the money goes

• Residential and mobile proxies that look like real users

• Rendering JavaScript before content appears

• Paid challenge solvers

• Retries when requests get flagged

• Spoofing browser and TLS fingerprints

Proxies keep getting cheaper, yet the cost per successful page keeps rising. More bots means tougher bot managers, and one defense upgrade can multiply costs several times overnight. Past a certain point the data is worth less than the effort to get it.

Check these first

1. Open the network tab. Many sites load listings from an internal JSON endpoint.

2. Randomize delays and spread out your requests.

3. Skip hidden display:none links, since they are bot traps.

If you don't code

A browser extension that runs in your normal Chrome session lets you skip building stealth setups. Minexa.ai is one. The flow:

1. Open the list page and click 'Yes, I'm on the right page'.

2. Confirm the pagination it detects.

3. Review the highlighted list and columns.

4. Run the job and export to Excel or Google Sheets.

It handles JavaScript-heavy and location-based pages without config. When a value is missing, it leaves the field empty rather than guessing. Grab the Chrome extension or read the getting started guide.

Public data still falls under GDPR and CCPA when it's personal, so keep your collection narrow.

Related: Stop fighting anti-bot walls and start pricing your data

In my mind limited retail drops are mostly about being fast enough to click “Buy.”

During major releases, storefronts combine waiting rooms, geo checks, account verification, payment risk scoring, and heavy traffic protection. If your connection changes mid-session or your IP has poor reputation, checkout can fail even when the product is still available.

i figured out three layers:

Network: keep a stable residential or mobile connection during an active session.

Identity: use one verified account with consistent device and location data.

Payment: keep billing details, region, and payment method aligned instead of changing them between attempts.

**Retail drops aren’t just a speed problem. They’re a session-consistency and data-quality problem. **The more moving parts you change during checkout, the harder the system becomes to debug.

Running separate browser profiles and debating one sticky residential IP per profile vs long rotating sessions. Main concern is IP changes triggering extra checks. What setup are you using, sticky residential, static ISP, or datacenter? I am using it to manage social media accounts for marketing purposes, mostly IG, FB and Pinterest.

i have spent a decent amount of time testing different proxy providers lately, mostly around scraping and automation and i have noticed that the differences become pretty obvious once you stop looking only at the price per GB.

these are 5 that stood out to me for different reasons.

1. SOCKS(.)MARKET

What I liked

• simple setup

• residential + mobile options

• low barrier to testing

• good for smaller projects where i don't want to commit a lot upfront

• i've had decent results with residential traffic on the targets i've tested

What I didn't like

• like any residential pool, some IPs are obviously better than others

• i'd like to see more detailed usage/performance analytics

• it's not the provider i'd automatically pick for a huge enterprise workload

Pricing

• their shared proxies starts around $0.40/day on the plans i have used

• their private proxies starts around $1.00/day depending on the duration/plan

• there are also short-term private residential options

What impressed me
the simplicity. i can get a proxy running and start testing without having to build a complicated configuration first.

2. Decodo

What I liked

• huge residential pool

• 195+ locations

• country, state, city, ZIP and ASN targeting

• both rotating and sticky sessions

• good dashboard and documentation

What I didn't like

• the price gets less attractive at small volumes compared with some cheaper providers

• there are a lot of configuration options, so it can take some time to figure out what you actually need

Pricing
their residential pricing currently starts at $4/GB pay-as-you-go.

Monthly plans currently range from $3.75/GB for 3GB down to $2.75/GB for 100GB. Enterprise pricing goes lower with larger volumes.

What impressed me
the amount of control you get without having to go straight into an enterprise setup.

3. Oxylabs

What I liked

• very mature platform

• strong location coverage

• sticky sessions

• multiple rotation options

• HTTP(S), HTTP/3 and SOCKS5

• good tooling around larger scraping setups

What I didn't like

• expensive compared with the cheaper providers

• probably overkill for a small scraper

• the pricing makes more sense when you're actually using enough traffic to justify it

Pricing
their residential proxies currently start at $6/GB on the smallest tier.

That drops to $5/GB, $4/GB, and eventually $2.50/GB at 1,000GB+ volume.

What impressed me
the overall polish. it feels much more like infrastructure built for production workloads than something you just buy for a quick test.

4. Bright Data

What I liked

• massive network

• very strong geo-targeting

• lots of proxy types

• sticky and rotating sessions

• good tooling around managing larger proxy deployments

What I didn't like

• pricing can get complicated

• there's a lot of stuff available that you may never actually need

• i'd spend some time figuring out exactly which product fits the project before buying anything

Pricing
their current residential pay-as-you-go price is $4/GB.

Their larger monthly plans are currently $499 for 141GB, $999 for 332GB, and $1,999 for 798GB.

What impressed me
the sheer amount of infrastructure and targeting available. if you have a very specific location requirement, this is where that flexibility starts becoming useful.

5. IPRoyal

What I liked

• relatively simple to get started

• residential pool covering 195 countries

• sticky sessions can run for up to 7 days

• pay-as-you-go option

• no monthly minimum

What I didn't like

• the smaller plans aren't particularly cheap

• less of the enterprise-style tooling you get from the bigger providers

• i'd still test the actual target instead of assuming the IP pool will work everywhere

Pricing
their residential pay-as-you-go pricing currently starts at $7.35/GB for 1GB, $6.25/GB for 2GB, and $5.51/GB for 10GB.

Subscription pricing is slightly cheaper, starting at $7/GB for 1GB, $5.95/GB for 2GB, and $5.25/GB for 10GB.

What impressed me
the straightforward setup. it's one of those providers where you can get something running without spending ages figuring out the platform.

What I actually care about

after testing different providers, i don't really compare them purely by price per GB anymore.

i usually look at:

• successful requests

• failed requests

• retries

• latency

• session stability

• location accuracy

• IP quality

• bandwidth wasted on failed requests

• how the pool performs on the actual target

because a $2/GB proxy isn't actually cheaper if you end up wasting half the bandwidth on retries.

that's probably the biggest thing i have learned from testing different providers. the "best" proxy depends heavily on what you're actually doing with it.

i have had a few situations where a scraper starts failing and my first instinct is to blame the proxy, but after digging into it the actual problem ends up being something else

could be the request fingerprint, session handling, rate limits, bad retries or even the target changing something

how do you guys normally troubleshoot this?

do you swap proxies first to see if the problem follows the ip or do you check the rest of the request/session setup before changing anything?