Data as of Nov 20, 2026

86.110.38.0/24

5 residential-proxy exits · 30 days

Server Farm LLC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Providers
46
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

1.2K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • Datarama
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HASDATA
  • HPROXY
  • IPFly
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonLabs
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSAVER
  • PROXYSCRAPE
  • Proxmint
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • PuraRoute
  • ResiProxies
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VitalExclusive

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
86.110.32.0/198,192EE-SERVERFARM-20050712Server Farm LLC (ORG-SFL10-RIPE) · EEALLOCATED PAJun 1, 2023abuse@serverfarm.ee
└ 86.110.38.0/24256SERVERFARM-CLIENTunknownASSIGNED PAMar 10, 2023abuse@serverfarm.ee
via EE-SERVERFARM-20050712

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
Apr 2022
Current origin since
Feb 2023 · 3.7 yr
Origin networks
2
Last change of origin
Feb 2023
Recorded history

History

Handoffs
1