Data as of Nov 15, 2026

86.102.157.0/24

4 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
34
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

674 observations

Proxy providers listing exits

  • 2Captcha
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • GSocks
  • GeekProxy
  • Geonix
  • GonzoProxy
  • Infatica
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • PSBProxy
  • PrivateByte
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • Proxyma
  • Q2IP
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
86.102.0.0/16
since Aug 2005
AS12332Residential4,692
24 always on
PJSC Rostelecom

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
86.102.0.0/1665,536RU-RTK-20050601PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJun 1, 2005abuse@rt.ru
└ 86.102.155.0 - 86.102.157.255768POL-LAZO-NETLazo node of electric communicationASSIGNED PAJan 14, 2007abuse@rt.ru
via RU-RTK-20050601

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

86.102.128.0/18

Routing history

Pattern
Stable
First seen
Aug 2005
Current origin since
Aug 2005 · 21 yr
Origin networks
1