Data as of Nov 10, 2026

83.243.124.0/22

5 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
5
0.49% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
6
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

51 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
83.243.124.0/2403
83.243.125.0/2401
83.243.126.0/2401

Proxy providers listing exits

  • AnyIP
  • FastProxy
  • FloppyData
  • LemonBright
  • ThunderProxy
  • 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
83.243.124.0/221,024FR-KNET-20180620K-Net SAS (ORG-KE6-RIPE) · FRALLOCATED PANov 15, 2024abuse@kwaoo.net
└ 83.243.124.0/24256KNET-CUSTOMERSKnet FAI RangeASSIGNED PADec 24, 2018abuse@kwaoo.net
via FR-KNET-20180620
└ 83.243.125.0/24256KNET-CUSTOMERSKnet FAI RangeASSIGNED PAFeb 4, 2019abuse@kwaoo.net
via FR-KNET-20180620
└ 83.243.126.0/24256KNET-CUSTOMERSKnet FAI RangeASSIGNED PAFeb 14, 2019abuse@kwaoo.net
via FR-KNET-20180620
└ 83.243.127.0/24256KNET-CUSTOMERSKnet FAI RangeASSIGNED PAFeb 14, 2019abuse@kwaoo.net
via FR-KNET-20180620

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