Fairvisor logoFAIRVISOR
Join Waitlist

Stop bots before they distort your data and your costs

ASN-aware rate policies, Tor and hosting tagging, and per-source burst shaping — so you can tell legitimate traffic from automated noise.

Deploy in shadow mode

What Fairvisor Does for AdTech & Media

ASN-Type Rate Policies

Apply different enforcement rules based on network origin:

  • Hosting ASN vs residential vs mobile carrier — different limits per class
  • Stricter quotas for datacenter-originated traffic by default
  • Custom trust tiers per ASN category or named AS

Tor Exit Node and Hosting Tagging

Tag and shape traffic from anonymizing infrastructure:

  • Real-time Tor exit node detection at the edge
  • Hosting/VPN/proxy tagging via IP intelligence
  • Route flagged traffic to degraded response playbooks without exposing detection logic

Burst Shaping

Absorb legitimate peaks without exposing the system to abuse spikes:

  • Sliding window + burst controls per identity and source type
  • Separate burst envelopes for known partners vs anonymous traffic
  • Cooldown enforcement after spike detection

Per-Source Traffic Limits

Differentiate by traffic origin at policy level:

  • Different rate budgets for organic, affiliate, and syndication sources
  • Hard caps on unverified or low-trust sources
  • Source attribution in enforcement logs

What Bot Traffic Looks Like

The traffic profile of a high-volume media API without source-aware enforcement:

Hosting ASN traffic

arrives in sustained bursts — not spikes. Scrapers running on cloud infrastructure send requests at consistent rates, 24/7, across rotating IPs within the same ASN range. IP-based blocks don’t work; new IPs appear within minutes.

Residential proxy traffic

looks almost indistinguishable from real users. The IPs are real residential addresses. The ASN is a consumer ISP. But the request rate, timing uniformity, and UA patterns reveal automation. → IP type policy docs

Tor exit node traffic

routes through a small, well-known set of IPs. Fairvisor tags it automatically. You decide whether to apply stricter limits or block entirely. → Bot categories

Click fraud patterns

combine multiple origin types: some residential, some hosting, always with request timing that’s too uniform to be human.

The point: you can’t solve this with IP blocklists. You need policy at the source type level.

Who This Is For

  • Ad serving and attribution APIs with open or semi-open access
  • Affiliate networks and publisher integrations
  • Media platforms with high request volume and bot exposure
  • Analytics and tracking APIs that need to separate signal from noise

FAQ

How does ASN-type enforcement work?

Fairvisor classifies inbound traffic by network origin: hosting/datacenter, residential ISP, mobile carrier, Tor exit node. Each class gets different rate limits. Hosting-originated traffic — where most bot infrastructure runs — gets stricter quotas by default. Fully configurable per named ASN or ASN category.

How are Tor exit nodes detected?

Fairvisor can classify and tag Tor/automation-related traffic signals at the edge, then apply policy responses such as separate limits, degraded playbooks, or blocking. Exact detection quality depends on dataset/version and deployment context. → Bot categories docs

Can I set different limits for affiliate vs organic traffic?

Yes. Source attribution is part of the policy model. Different rate budgets per traffic source type — organic, affiliate, syndication, unverified. Source context appears in enforcement logs for attribution reporting and anomaly investigation.

What happens during a legitimate traffic spike?

Burst controls absorb short-duration peaks within configured limits without triggering enforcement. Sustained burst beyond the window triggers staged degradation: warn → throttle → reject. Shadow mode lets you calibrate thresholds against real traffic patterns before enforcement is live.

Why teams choose Fairvisor

Edge enforcement before your app sees it

ASN-type policies and Tor/hosting tagging that act on traffic before it reaches your application layer.

Source-aware rate policies

Differentiate residential, hosting, and datacenter traffic with per-class enforcement rules — not just IP-level blocks.

Bot suppression before it corrupts signals

Burst shaping and source limits that keep automated traffic from distorting your analytics and attribution.

Enforce traffic source policies at the edge

Deploy in shadow mode
LLM-friendly markdown version

Also relevant

For API-First SaaS

Per-tenant limits, noisy neighbor protection, and tiered plan enforcement.

For Content Sites

AI crawler detection and rate limits for docs and developer portals.

For SRE

Sub-millisecond enforcement, graceful degradation, and SLO alerting.