Data as of Nov 11, 2026

68.160.158.0/24

4 residential-proxy exits · 30 days

Verizon Business

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
2
50% of its exits
Providers
38
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

7.7K observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FloppyData
  • GloryCloud
  • IPRoyal
  • Infatica
  • LemonBright
  • MangoProxy
  • NextProxy
  • NovaProxy
  • Oxylabs
  • PrivateByte
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Q2IP
  • SPYDERPROXY_PREMIUM
  • Shifter
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
68.160.0.0/14
since Feb 2026
AS701Residential2,379
416 always on
Verizon Business

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
68.160.0.0/14262,144VIS-68-160Verizon Business (MCICS) · USDirect AllocationAug 30, 2002abuse@verizon.com
└ 68.160.128.0/1816,384VZ-DSLDIAL-BSTNMA-18Verizon Internet Services (C00410030) · USReassignedNov 6, 2002abuse@verizon.com
via VIS-68-160

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

68.160.128.0/19

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2013 · 13 yr
Origin networks
3
Last change of origin
May 2013
Recorded history

History

Handoffs
2