Data as of Nov 15, 2026

81.24.82.0/24

6 residential-proxy exits · 30 days

Subnet LLC

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

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Providers
36
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

1.2K observations

Proxy providers listing exits

  • 2Captcha
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.24.80.0/21
since May 2018
AS39434Residential113
9 always on
Subnet LLC

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
81.24.80.0/204,096RU-SUBNET-20060221Subnet LLC (ORG-SL529-RIPE) · RUALLOCATED PAMay 4, 2017abuse@subnet05.ru
└ 81.24.82.0/23512SUBNET05-NETOptika-Telekom LtdASSIGNED PAFeb 21, 2006abuse@subnet05.ru
via RU-SUBNET-20060221

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Mar 2010
Current origin since
Mar 2010 · 17 yr
Origin networks
1