LAYER3 INTEL
Get started
Sign in
Data as of Nov 11, 2026

81.2.10.0/24

57 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
AS12389
Type
Business
88% of it

Residential-proxy exits

Proxy exits
57
22% of its addresses · 30 days
Providers
56
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

4.5K observations
  • Residential
  • Business

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • SwiftProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.2.0.0/19
since May 2005
AS12332Residential576
2 always on
PJSC Rostelecom
81.2.0.0/18
since May 2005
AS12332Residential1,298
2 always on
PJSC Rostelecom

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.2.0.0/1816,384RU-RTK-20020304PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAMar 4, 2002abuse@rt.ru
└ 81.2.10.0/2816POL-Chukov-NETChukov Private EstablishmentASSIGNED PAJan 16, 2007abuse@rt.ru
via RU-RTK-20020304
└ 81.2.10.32/2732POL-NURISOFT-NETNurisoftASSIGNED PAMay 8, 2003abuse@rt.ru
via RU-RTK-20020304
└ 81.2.10.64/2732POL-VLADHLEB-NETJSC VladhlebASSIGNED PASep 30, 2002abuse@rt.ru
via RU-RTK-20020304
└ 81.2.10.96/2816POL-RTKTRANSIT-NETRTK-TransitASSIGNED PAAug 27, 2008abuse@rt.ru
via RU-RTK-20020304
└ 81.2.10.112/2816POL-SINTOZA-NETSintoza LTDASSIGNED PAMay 14, 2008abuse@rt.ru
via RU-RTK-20020304
└ 81.2.10.128/2816POL-AUTOMAT-NETAutomat, LTDASSIGNED PAJun 19, 2008abuse@rt.ru
via RU-RTK-20020304
└ 81.2.10.144/2816POL-RCB-NETRoyal Credit BankASSIGNED PAApr 11, 2008abuse@rt.ru
via RU-RTK-20020304
└ 81.2.10.160/2816POL-VLADEXPRESS-NETVlad-Express, LTDASSIGNED PASep 27, 2008abuse@rt.ru
via RU-RTK-20020304
└ 81.2.10.176/2816POL-ALS-NETALS, ltd.ASSIGNED PAMar 31, 2009abuse@rt.ru
via RU-RTK-20020304
└ 81.2.10.192/2732POL-MCHS-NETMChSASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20020304
└ 81.2.10.240/2816POL-OLGAVLAD-NETOlga-VladASSIGNED PASep 10, 2007abuse@rt.ru
via RU-RTK-20020304

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Business22488%11
Residential3213%2

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jul 2020
Current origin since
Jul 2020 · 6.3 yr
Origin networks
1