Data as of Nov 16, 2026

68.160.154.0/24

8 residential-proxy exits · 30 days

Verizon Business

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
2
25% of its exits
Providers
41
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

6.0K observations

Proxy providers listing exits

  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • ColaProxy
  • CoreProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MoMoProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Q2IP
  • RainProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
68.160.0.0/14
since Feb 2026
AS701Residential2,387
436 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