Data as of Nov 11, 2026

68.160.185.0/24

6 residential-proxy exits · 30 days

Verizon Business

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

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Providers
34
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

2.6K observations

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • ColaProxy
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MrScraper
  • NovaProxy
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • RoamProxy
  • Shifter
  • Thordata
  • VitalExclusive
  • YumiProxy

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.160.0/19

Routing history

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

History

Handoffs
2