Data as of Nov 20, 2026

208.250.64.0/21

3 residential-proxy exits · 30 days

Verizon Business

Announcement
this exact prefix
No RPKI
Announced by
Type
Internet provider
73% of it
Recent change
New origin Jul 2026
its first announcement on record

Residential-proxy exits

Proxy exits
3
0.15% of its addresses · 30 days
Always-on exits
1
33% of its exits
Spread
3 of 8
/24s with at least one exit
Providers
32
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

4.0K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
208.250.64.0/2411
208.250.66.0/2401
208.250.68.0/2401

Proxy providers listing exits

  • Ake.net
  • AnyIP
  • BirdProxies
  • Byteful
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FastProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GloryCloud
  • HASDATA
  • IP2WORLD
  • IPMUSK
  • Infatica
  • LemonPrime
  • LudaxProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • ProxyRack
  • Proxyma
  • Q2IP
  • QUANTICDATA
  • RainProxy
  • SOTAPROXY
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
208.192.0.0/10AS701Internet provider633
29 always on
Verizon Business
More specific

Announcements inside

PrefixOriginTypeHolderRPKI
208.250.70.0/24
since Nov 2017
AS15134BusinessVerizon Business

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
208.192.0.0/104,194,304UUNET1996BVerizon Business (MCICS) · USDirect AllocationMay 8, 1996abuse@verizon.com
└ 208.250.64.0/298UU-208-250-64-D11unknown———
└ 208.250.64.8/298UU-208-250-64-8unknown———
└ 208.250.64.16/298UU-208-250-64-16-D8unknown———
└ 208.250.64.24/298UU-208-250-64-24unknown———
└ 208.250.64.32/2732UU-208-250-64-32-D1unknown———
└ 208.250.64.64/2664UU-208-250-64-64unknown———
└ 208.250.64.136/298UU-208-250-64-136unknown———
└ 208.250.64.144/298UU-208-250-64-144unknown———
└ 208.250.64.152/298UU-208-250-64-152-D2unknown———
└ 208.250.64.208/298UU-208-250-64-208unknown———
└ 208.250.64.224/2732UU-208-250-64-224unknown———
└ 208.250.65.0/25128UU-208-250-65-D3unknown———
└ 208.250.65.128/2732UU-208-250-65-128unknown———
└ 208.250.65.160/2732UU-208-250-65-160unknown———
└ 208.250.65.224/2816UU-208-250-65-224unknown———
└ 208.250.65.240/298UU-208-250-65-240unknown———
└ 208.250.65.248/298UU-208-250-65-248-D3unknown———
└ 208.250.67.0/298UU-208-250-67unknown———
└ 208.250.67.8/298UU-208-250-67-8-D4unknown———
└ 208.250.67.40/298UU-208-250-67-40-D3unknown———
└ 208.250.67.48/298NET-208-250-67-48-1unknown———
└ 208.250.67.56/298UU-208-250-67-56-D3unknown———
└ 208.250.67.64/2732UU-208-250-67-64-D8unknown———
└ 208.250.67.96/2732UU-208-250-67-96-D2unknown———
└ 208.250.67.96/2732INTER-TEL-NETSOLUTIONSunknown———
└ 208.250.67.128/2732UU-208-250-67-128-D2unknown———
└ 208.250.67.160/298UU-208-250-67-160unknown———
└ 208.250.67.168/298UU-208-250-67-168unknown———
└ 208.250.67.176/298UU-208-250-67-176unknown———
└ 208.250.67.184/298UU-208-250-67-184unknown———
└ 208.250.67.192/2732UU-208-250-67-192unknown———
└ 208.250.67.224/2732VZBCUSTunknown———
└ 208.250.68.0/2732UU-208-250-68unknown———
└ 208.250.68.40/298UU-208-250-68-40unknown———
└ 208.250.68.48/2816VZBCUSTunknown———
└ 208.250.68.64/2664UU-208-250-68-64unknown———
└ 208.250.68.128/298UU-208-250-68-128unknown———
└ 208.250.68.136/298UU-208-250-68-136-D2unknown———
└ 208.250.68.144/298UU-208-250-68-144-D7unknown———
└ 208.250.68.168/298UU-208-250-68-168-D3unknown———
└ 208.250.68.184/298UU-208-250-68-184unknown———
└ 208.250.68.184/298NETWOLVES-208-250-68-184unknown———
└ 208.250.68.192/2664VZBCUSTunknown———
└ 208.250.69.0/2816UU-208-250-69-D9unknown———
└ 208.250.69.16/298UU-208-250-69-16unknown———
└ 208.250.69.40/298UU-208-250-69-40unknown———
└ 208.250.69.80/298UU-208-250-69-80-D6unknown———
└ 208.250.69.88/298UU-208-250-69-88unknown———
└ 208.250.69.104/298UU-208-250-69-104unknown———
└ 208.250.69.112/298UU-208-250-69-112unknown———
└ 208.250.69.120/298UU-208-250-69-120-D3unknown———
└ 208.250.69.160/298UU-208-250-69-160unknown———
└ 208.250.69.168/298UU-208-250-69-168unknown———
└ 208.250.69.248/298UU-208-250-69-248unknown———
└ 208.250.70.0/24256UU-208-250-70Prince William County Service Authority (C06533131) · USReassignedJun 1, 2017abuse@verizon.com
via UUNET1996B
└ 208.250.71.0/24256UU-208-250-71unknown———

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

2,048 addresses
TypeAddressesShareRanges
Internet provider1,48873%7
Business56027%9

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jul 2026
Current origin since
Jul 2026 · 5 mo
Origin networks
1