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

86.102.187.0/24

1 residential-proxy exit · 30 days

PJSC Rostelecom

Announcement
86.102.128.0/18
RPKI valid
Announced by
AS12332
Type
Residential
94% of it

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Always-on exits
1
100% of its exits
Providers
19
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

505 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • FlashProxy
  • GonzoProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • 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.187.0/2816POL-MORONLTD-NETMoron, LtdASSIGNED PAMay 22, 2012abuse@rt.ru
via RU-RTK-20050601
└ 86.102.187.128/25128POL-PPPOE-NET-UNLDynamic Broadband Clients.ASSIGNED PAJul 18, 2012abuse@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.

Composition

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

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Residential24094%1
Business166.3%1

Network & registry

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