Data as of Nov 12, 2026

45.15.60.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
Always-on exits
1
33% of its exits
Spread
2 of 4
/24s with at least one exit
Providers
23
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

7.5K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
45.15.61.0/2412
45.15.63.0/2401

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • Infatica
  • KocerRoxy
  • Oxylabs
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • StrikeProxy
  • Thordata
  • ThunderProxy

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
45.15.60.0/221,024FR-KNET-20190510K-Net SAS (ORG-KE6-RIPE) · FRALLOCATED PANov 15, 2024abuse@kwaoo.net
└ 45.15.60.0/24256KNET-CUSTOMERSKnet FAI RangeASSIGNED PANov 18, 2019abuse@kwaoo.net
via FR-KNET-20190510
└ 45.15.61.0/24256KNET-CUSTOMERSKnet FAI RangeASSIGNED PANov 18, 2019abuse@kwaoo.net
via FR-KNET-20190510
└ 45.15.62.0/24256KNET-CUSTOMERSKnet FAI RangeASSIGNED PANov 18, 2019abuse@kwaoo.net
via FR-KNET-20190510
└ 45.15.63.0/24256KNET-CUSTOMERSKnet FAI RangeASSIGNED PANov 18, 2019abuse@kwaoo.net
via FR-KNET-20190510

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