Data as of Nov 13, 2026

64.72.106.0/24

2 residential-proxy exits · 30 days

isp.net

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Always-on exits
1
50% of its exits
Providers
20
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

8.2K observations

Proxy providers listing exits

  • Ake.net
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FlexyProxies
  • GloryCloud
  • LemonBright
  • LudaxProxy
  • MoMoProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • VibeProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
64.72.96.0/20
since Feb 2010
AS27501Residential40
13 always on
isp.net

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
64.72.96.0/204,096LASVEGASNETWORK2isp.net (IIL-168) · USDirect AllocationFeb 4, 2010arin@isp.net
└ 64.72.106.0/2425664721060252SUBNETunknownReassignedFeb 5, 2012arin@isp.net
via LASVEGASNETWORK2

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Oct 2025 · 1.0 yr
Origin networks
2
Last change of origin
Jul 2017
Recorded history

History

Handoffs
1