LAYER3 INTEL
Get started
Sign in
Data as of Nov 15, 2026

216.17.0.0/19

3 residential-proxy exits · 30 days

US Internet Corp

Announcement
this exact prefix
RPKI valid
Announced by
AS10242
Type
Residential
71% of it

Residential-proxy exits

Proxy exits
3
0.04% of its addresses · 30 days
Spread
2 of 32
/24s with at least one exit
Providers
24
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

122 observations
  • Residential
  • Business

/24s with the most always-on exits

/24Always-on exitsProxy exits
216.17.5.0/2402
216.17.22.0/2401

Proxy providers listing exits

  • BirdProxies
  • Bright Data
  • CatProxies
  • ColaProxy
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • GSocks
  • Geonode
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • NodeProxy
  • NovaProxy
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
216.17.0.0/24
since Mar 2017
AS10242ResidentialUS Internet Corp
216.17.1.0/24
since Mar 2017
AS10242ResidentialUS Internet Corp
216.17.8.0/24
since Mar 2023
AS396410BusinessUS Internet Corp

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
216.17.0.0 - 216.17.95.25524,576USINET-BLKUS Internet Corp (USIC) · USDirect AllocationJul 10, 1998hostmaster@usinternet.com
└ 216.17.0.0/24256USI-NETBLK-0-0Usinternet Corp (C00782671) · USReassignedMar 10, 2004hostmaster@usinternet.com
via USINET-BLK
└ 216.17.2.0/24256USI-NETBLK-2-0unknown———
└ 216.17.3.0/24256USI-NETBLK-3-0unknown———
└ 216.17.4.0/24256USI-NETBLK-4-0unknown———
└ 216.17.5.0/24256USI-NETBLK-5-0unknown———
└ 216.17.6.0/24256USI-NETBLK-6-0unknown———
└ 216.17.8.0/24256USI-NETBLK-8-0Code 42 (C04661216) · USReassignedAug 5, 2013hostmaster@usinternet.com
via USINET-BLK
└ 216.17.9.0/25128USI-NETBLK-9-0unknown———
└ 216.17.9.128/25128USI-NETBLK-9-128unknown———
└ 216.17.10.0/2664USI-NETBLK-10-0unknown———
└ 216.17.10.128/2664USI-NETBLK-10-128unknown———
└ 216.17.11.0/24256USI-NETBLK-11-0unknown———
└ 216.17.13.40/298USI-NETBLK-13-40unknown———
└ 216.17.13.48/298USI-NETBLK-13-48unknown———
└ 216.17.13.56/298USI-NETBLK-13-56unknown———
└ 216.17.13.64/298USI-NETBLK-13-64unknown———
└ 216.17.13.80/298USI-NETBLK-13-80unknown———
└ 216.17.13.88/298USI-NETBLK-13-88unknown———
└ 216.17.13.104/298USI-NETBLK-13-104unknown———
└ 216.17.13.120/298USI-NETBLK-13-120unknown———
└ 216.17.13.128/298USI-NETBLK-13-128unknown———
└ 216.17.13.176/298USI-NETBLK-13-176unknown———
└ 216.17.13.184/298USI-NETBLK-13-184unknown———
└ 216.17.13.192/298USI-NETBLK-13-192unknown———
└ 216.17.13.200/298USI-NETBLK-13-200unknown———
└ 216.17.13.208/298USI-NETBLK-13-208unknown———
└ 216.17.13.216/298USI-NETBLK-13-216unknown———
└ 216.17.13.232/298USI-NETBLK-13-232unknown———
└ 216.17.14.0/24256USI-NETBLK-14-0unknown———
└ 216.17.15.0/298WINDPOWER001unknown———
└ 216.17.15.8/298USI-NETBLK-15-8unknown———
└ 216.17.15.56/298USI-NETBLK-15-56unknown———
└ 216.17.15.80/298USI-NETBLK-15-80unknown———
└ 216.17.15.96/298USI-NETBLK-15-96unknown———
└ 216.17.15.104/298USI-NETBLK-15-104unknown———
└ 216.17.15.120/298USI-NETBLK-15-120unknown———
└ 216.17.15.144/298USI-NETBLK-15-144unknown———
└ 216.17.15.152/298USI-NETBLK-15-152unknown———
└ 216.17.15.160/298USI-NETBLK-15-160unknown———
└ 216.17.15.168/298USI-NETBLK-15-168unknown———
└ 216.17.15.200/298USI-NETBLK-15-200unknown———
└ 216.17.15.208/298USI-NETBLK-15-208unknown———
└ 216.17.15.224/298USI-NETBLK-15-224unknown———
└ 216.17.16.0 - 216.17.16.254255ARBITRADEBLKunknown———
└ 216.17.17.0/25128USI-NETBLK-17-0unknown———
└ 216.17.18.128/25128USI-NETBLK-18-128unknown———
└ 216.17.19.0/2664NETBLK-19-0unknown———
└ 216.17.19.192/2664USI-NETBLK-19-192unknown———
└ 216.17.20.0/24256USI-NETBLK-20-0unknown———
└ 216.17.21.32/2732USI-NETBLK-21-32unknown———
└ 216.17.21.96/2732USI-NETBLK-21-96unknown———
└ 216.17.21.128/2732USI-NETBLK-21-128unknown———
└ 216.17.21.192/2732USI-NETBLK-21-192unknown———
└ 216.17.21.224/2732USI-NETBLK-21-224unknown———
└ 216.17.22.0/2664USI-NETBLK-22-0unknown———
└ 216.17.22.64/2664USI-NETBLK-22-64unknown———
└ 216.17.23.192/2664USI-NETBLK-23-192unknown———
└ 216.17.24.0/24256USI-NETBLK-24-0unknown———
└ 216.17.25.32/2732USI-NETBLK-25-32unknown———
└ 216.17.25.64/2732USI-NETBLK-25-64unknown———
└ 216.17.25.224/2732USI-NETBLK-25-224unknown———
└ 216.17.26.0/24256SHOPNBC-USI-NETBLK-26-0unknown———
└ 216.17.27.0/24256USI-NETBLK-27-0unknown———
└ 216.17.28.32/2816USI-NETBLK-28-32unknown———
└ 216.17.28.48/2816USI-NETBLK-28-48unknown———
└ 216.17.28.80/2816USI-NETBLK-28-80unknown———
└ 216.17.28.128/2816USI-NETBLK-28-128unknown———
└ 216.17.28.144/2816USI-NETBLK-28-144unknown———
└ 216.17.28.160/2816USI-NETBLK-28-160unknown———
└ 216.17.28.176/2816USI-NETBLK-28-176unknown———
└ 216.17.28.192/2816USI-NETBLK-28-192unknown———
└ 216.17.28.208/2816USI-NETBLK-28-208unknown———
└ 216.17.28.224/2816USI-NETBLK-28-224unknown———
└ 216.17.28.240/2816USI-NETBLK-28-240unknown———
└ 216.17.29.0/2816USI-NETBLK-29-0unknown———
└ 216.17.29.64/2816USI-NETBLK-29-64unknown———
└ 216.17.29.112/2816USI-NETBLK-29-112unknown———
└ 216.17.29.160/2816USI-NETBLK-29-160unknown———
└ 216.17.29.192/2816USI-NETBLK-29-192unknown———
└ 216.17.29.224/2816USI-NETBLK-29-224unknown———
└ 216.17.29.240/2816USI-NETBLK-29-240unknown———
└ 216.17.30.32/2816USI-NETBLK-30-32unknown———
└ 216.17.30.48/2816USI-NETBLK-30-48unknown———
└ 216.17.30.112/2816USI-NETBLK-30-112unknown———
└ 216.17.30.144/2816USI-NETBLK-30-144unknown———
└ 216.17.30.208/2816USI-NETBLK-30-208unknown———
└ 216.17.31.0/24256USI-NETBLK-31-0unknown———

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

8,192 addresses
TypeAddressesShareRanges
Residential5,85671%41
Business2,08025%73
Hosting2563.1%1

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1