Data as of Nov 11, 2026

86.80.231.0/24

8 residential-proxy exits · 30 days

KPN B.V.

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
2
25% of its exits
Providers
47
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

3.9K observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeMaven
  • NovProxy
  • NovaProxy
  • Oxylabs
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • YumiProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
86.80.0.0 - 86.90.255.255720,896NL-WAPI-20050323KPN B.V. (ORG-WAPI1-RIPE) · NLALLOCATED PAApr 24, 2024abuse@kpn.com
└ 86.80.0.0/1665,536KPNCustomersASSIGNED PAJun 9, 2005abuse@kpn.com
via NL-WAPI-20050323

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 86.80.0.0/13

86.80.0.0/13

Routing history

Pattern
Stable
First seen
Aug 2006
Current origin since
Mar 2024 · 2.7 yr
Origin networks
2
Last change of origin
Mar 2015
Recorded history

History

Handoffs
1