Data as of Nov 14, 2026

217.26.96.0/20

35 residential-proxy exits · 30 days

Solcon Internetdiensten B.V. · space held by KPN B.V.

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

Residential-proxy exits

Proxy exits
35
0.85% of its addresses · 30 days
Always-on exits
6
17% of its exits
Spread
7 of 16
/24s with at least one exit
Providers
68
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

9.9K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonode
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • Kookey
  • LemonBright
  • LightningProxies
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy

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
217.26.96.0/204,096NL-WAPI-20100607KPN B.V. (ORG-WAPI1-RIPE) · NLALLOCATED PAJun 7, 2010abuse@kpn.com
└ 217.26.96.0/212,048SOLCON-FTTHunknownASSIGNED PAAug 24, 2012abuse@kpn.com
via NL-WAPI-20100607
└ 217.26.104.0/212,048SOLCON-FTTHunknownASSIGNED PAJun 3, 2019abuse@kpn.com
via NL-WAPI-20100607

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2019 · 7.5 yr
Origin networks
4
Last change of origin
May 2019
Recorded history

History

Handoffs
3