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

82.162.57.0/24

11 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
11
4.3% of its addresses · 30 days
Always-on exits
3
27% of its exits
Providers
30
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

4.3K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • GonzoProxy
  • HydraProxy
  • IPPeak
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyStyler
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
82.162.0.0/18
since May 2005
AS12332Residential973
15 always on
PJSC Rostelecom
82.162.0.0/16
since May 2005
AS12332Residential3,000
121 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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