Data as of Nov 16, 2026

82.162.60.0/24

19 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
19
7.4% of its addresses · 30 days
Always-on exits
1
5.3% of its exits
Providers
51
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

2.5K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • AETHYN_ELITE
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GEEKPROXY_FLEX
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • MoMoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • PSBProxy
  • PrivateByte
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyStyler
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
82.162.0.0/18
since May 2005
AS12332Residential951
16 always on
PJSC Rostelecom
82.162.0.0/16
since May 2005
AS12332Residential2,970
131 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
82.162.0.0/1665,536RU-RTK-20030716PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJul 16, 2003abuse@rt.ru
└ 82.162.56.0/212,048POL-PPPOE-NET-UNLDynamic Broadband Clients.ASSIGNED PAJun 28, 2012abuse@rt.ru
via RU-RTK-20030716

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