Data as of Nov 15, 2026

81.24.82.0/23

6 residential-proxy exits · 30 days

Subnet LLC

Announcement
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
6
1.2% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
37
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
  • GEEKPROXY_FLEX
  • 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

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
81.24.82.0/24
since Mar 2010
AS39434Residential6Subnet LLC

Registrations in this block

The registry's network records over this block, widest first, each 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

Who has announced 81.24.80.0/21

81.24.80.0/21

Routing history

Pattern
Stable
First seen
May 2018
Current origin since
May 2018 · 8.5 yr
Origin networks
1