By Ajay Mishra, Team BeastBrowser

The short answer — survey already completed ip: panels don't just block repeated IPs — they run three dedupe modes. Exact-match blocks the same IP retaking a survey; subnet dedupe flags different IPs from the same network block; velocity dedupe flags too many completions from one IP too fast. Your home Wi-Fi, your carrier's shared IPs, and your VPN exit node all trip different modes.

How this differs from the basics: the companion post "You've Already Completed This Survey" covers the taker's-eye view (the IP + cookie + fingerprint triple check). This one goes deeper into the dedupe machinery itself — the part panel operators configure and fraud teams tune.

Why it matters: most people try to beat dedupe with a new IP and fail anyway, because they beat one mode while tripping another.

The three dedupe modes

Mode What it checks What trips it
Exact-match Has this exact IP completed this survey ID before? Same household retaking; shared/carrier IPs
Subnet / range Are completions clustering inside one /24 or ASN? VPN exit nodes; datacenter ranges; CGNAT pools
Velocity How many completes per IP per hour/day? Farms; shared office IPs; aggressive routers

Picture it as three gates in a row: every completion passes exact-match first, then subnet, then velocity. Passing gate one and tripping gate two is still a rejection — which is why single-fix attempts keep failing.

Why your home IP betrays you (it's not personal)

Three everyday situations trip exact-match dedupe without any wrongdoing:

  • One household, one public IP. Your router gives the whole house a single public IP. Your spouse completes a survey Tuesday; you try the same study Wednesday — the panel sees the same IP. From its side, that's one respondent twice.
  • Carrier-grade NAT. Mobile carriers pack hundreds of subscribers behind a handful of public IPs. Someone across town on your carrier completed it; now you're blocked too. This is the most "random-feeling" rejection in surveys.
  • Dynamic IP recycling. Your ISP reassigns your IP periodically. The previous holder of your "new" IP completed surveys on it — you inherit their history.

None of these are your fault. All of them are indistinguishable from fraud to an automated system — which is exactly why the fix has to be structural, not behavioral.

Why VPNs make dedupe worse

A VPN concentrates thousands of users onto a small set of exit IPs — the perfect trigger for subnet and velocity dedupe simultaneously. Fraud systems also maintain lists of commercial VPN ASNs, so the IP is pre-scored before the survey even loads. You traded one flag (your home IP's history) for three worse ones. The full VPN vs proxy breakdown.

The fix: one sticky residential IP per identity

What actually passes all three modes:

  • Residential, not datacenter. Consumer-ISP ASNs aren't pre-flagged; they look like ordinary respondents because they are ordinary respondents' networks.
  • Sticky, not rotating. The IP must not change mid-survey — a swap halfway through is an instant kill, and rapid rotation trips velocity dedupe on its own.
  • One IP per profile, permanently mapped. Profile A always exits from IP A. That mapping is what makes each identity look like a separate, stable human.

Recommended providers with sticky residential and city targeting: Evomi and Floppydata — compared with live pricing in Evomi vs Floppydata, and the buying guide in Best Proxy for Paid Surveys 2026. The session mechanics: sticky vs rotating explained.

The household setup that actually works

Panels expect households — several real people behind one IP is normal life, and most panels' exact-match dedupe is per-survey, not per-panel. What kills household setups is everyone sharing one browser: same fingerprint across "different" people is the giveaway, not the IP. Give each person their own isolated browser profile (own fingerprint, own cookies), and add individual sticky residential IPs for the serious earners. The panel sees what you actually are: several people, not one person faking several.

FAQ

Will changing my IP let me retake a survey?
Technically the exact-match check resets — but the fingerprint check (layer 1) doesn't, and retaking surveys you're not eligible for violates panel terms. Don't.

How long do panels remember IPs?
Varies by panel — some per-study, some rolling 30–90 day windows, some indefinitely for fraud-flagged ranges. There's no universal answer; assume long.

Does IPv6 change anything?
Marginally — the larger address space makes exact-match slightly less collision-prone, but panels dedupe on /64 subnets precisely to close that gap.

Is one static IP per account better than sticky rotating?
For your highest-value, longest-lived accounts, yes — the same IP every login is the strongest consistency signal. For the fleet, sticky sessions are the practical standard.

Next: IP is only half of layer 2 — what fraud tools actually see when you use a VPN, proxy, or location spoofer. Full map: Survey Security in 2026.

Question: which dedupe mode do you think has burned you most — exact-match (household/carrier), subnet (VPN), or velocity? Describe the pattern in the comments.

Ajay Mishra
Team, BeastBrowser · Updated October 2026

Sources & Credits

  • BeastBrowser survey-security hub: Survey Security in 2026 and the companion proxy cluster
  • Evomi pricing — residential $0.49/GB on the 100 GB plan, mobile $2.20–$3.98/GB, static residential from $1.00/IP — verified live 2026-10-23 — https://evomi.com/pricing
  • Floppydata pricing — residential & mobile flat $1/GB, static residential $1.79/IP — verified live 2026-10-23 — https://floppydata.com/pricing