Data as of Nov 14, 2026

185.207.80.0/22

2 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
2
0.20% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
5
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

35 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.207.81.0/2401
185.207.82.0/2401

Proxy providers listing exits

  • FastProxy
  • LemonBright
  • Proxiware
  • 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
185.207.80.0/221,024FR-KNET-20170608K-Net SAS (ORG-KE6-RIPE) · FRALLOCATED PAApr 16, 2020abuse@kwaoo.net
└ 185.207.80.0/24256KNET-CUSTOMERSKnet FAI RangeASSIGNED PAJun 8, 2017abuse@kwaoo.net
via FR-KNET-20170608
└ 185.207.81.0/24256KNET-CUSTOMERSKnet FAI RangeASSIGNED PAJun 8, 2017abuse@kwaoo.net
via FR-KNET-20170608
└ 185.207.82.0/24256KNET-CUSTOMERSKnet FAI RangeASSIGNED PAJun 8, 2017abuse@kwaoo.net
via FR-KNET-20170608
└ 185.207.83.0/24256KNET-CUSTOMERSKnet FAI RangeASSIGNED PAJun 8, 2017abuse@kwaoo.net
via FR-KNET-20170608

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
Dec 2025
Current origin since
Dec 2025 · 11 mo
Origin networks
1