Data as of Nov 12, 2026

171.22.0.0/22

3 residential-proxy exits · 30 days

K-Net SAS

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

Residential-proxy exits

Proxy exits
3
0.29% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
31
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

186 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
171.22.3.0/2402
171.22.0.0/2401

Proxy providers listing exits

  • 2Extract
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FlexyProxies
  • GonzoProxy
  • IPOasis
  • IPRoyal
  • Infatica
  • LemonBright
  • MangoProxy
  • NextProxy
  • NovaProxy
  • Proxy-Seller
  • Proxy302
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Shifter
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • ThunderProxy
  • VitalData
  • VitalExclusive

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
171.22.0.0/221,024FR-KNET-20190129K-Net SAS (ORG-KE6-RIPE) · FRALLOCATED PANov 15, 2024abuse@kwaoo.net
└ 171.22.0.0/24256KNET-CUSTOMERSKnet FAI RangeASSIGNED PAJun 14, 2019abuse@kwaoo.net
via FR-KNET-20190129
└ 171.22.1.0/24256KNET-CUSTOMERSKnet FAI RangeASSIGNED PAJun 14, 2019abuse@kwaoo.net
via FR-KNET-20190129
└ 171.22.2.0/24256KNET-CUSTOMERSKnet FAI RangeASSIGNED PAJun 14, 2019abuse@kwaoo.net
via FR-KNET-20190129
└ 171.22.3.0/24256KNET-CUSTOMERSKnet FAI RangeASSIGNED PAJun 14, 2019abuse@kwaoo.net
via FR-KNET-20190129

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
Jun 2019
Current origin since
Jun 2019 · 7.4 yr
Origin networks
1