Data as of Nov 13, 2026

148.170.67.0/24

5 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
5
2.0% of its addresses · 30 days
Always-on exits
2
40% of its exits
Providers
36
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

9.1K observations

Proxy providers listing exits

  • Ake.net
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlexyProxies
  • Geonode
  • GloryCloud
  • IPFly
  • IPRoyal
  • InfiniteProxies
  • LemonBright
  • LudaxProxy
  • MoMoProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
148.170.64.0/19
since Sep 2019
AS27501Residential46
11 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
148.170.64.0/198,192ISPNET-148-170-64isp.net (IIL-168) · USDirect AllocationSep 9, 2019arin@isp.net
└ 148.170.67.0/24256LVNET-148-170-67-0Lvnet LLC (C07424035) · USReassignedSep 10, 2019arin@isp.net
via ISPNET-148-170-64

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
Jun 2025 · 1.4 yr
Origin networks
2
Last change of origin
Oct 2020
Recorded history

History

Handoffs
1