Data as of Nov 13, 2026

216.255.0.0/24

6 residential-proxy exits · 30 days

Horizon Telcom Inc. · space held by Com Net, Inc.

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

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
4
67% of its exits
Providers
37
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

19K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • ColaProxy
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • IPRoyal
  • Infatica
  • LemonBright
  • LudaxProxy
  • NodeMaven
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
216.255.0.0/18
since May 2005
AS7106Residential195
35 always on
Com Net, Inc.

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
216.255.0.0/1816,384INDEPENDENTS-3BLKCom Net, Inc. (BNET) · USDirect AllocationApr 16, 2001abuse@cniteam.com
└ 216.255.0.0/212,048HORIZON-NRP1-VDSLHorizon Telcom Inc. (C01532571) · USReassignedJan 3, 2007abuse@cniteam.com
via INDEPENDENTS-3BLK

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

216.255.0.0/21

Routing history

Pattern
Stable
First seen
Jan 2007
Current origin since
Dec 2015 · 11 yr
Origin networks
2
Last change of origin
Dec 2015
Recorded history

History

Handoffs
1