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

86.102.91.0/24

45 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
45
18% of its addresses · 30 days
Providers
57
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

4.0K observations
  • Residential
  • Business

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYLANE
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
86.102.64.0/18
since Aug 2005
AS12332Residential246
13 always on
PJSC Rostelecom
86.102.0.0/16
since Aug 2005
AS12332Residential4,714
29 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
86.102.0.0/1665,536RU-RTK-20050601PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJun 1, 2005abuse@rt.ru
└ 86.102.91.0/2816POL-RESSICOR-NETRessi-Cor InvestASSIGNED PADec 29, 2006abuse@rt.ru
via RU-RTK-20050601
└ 86.102.91.32/2816POL-TNVLADIVOSTOK-NETTelenedelya Vladivostok, LTDASSIGNED PADec 10, 2008abuse@rt.ru
via RU-RTK-20050601
└ 86.102.91.48/2816POL-KNIGOMIR-NETKnigomirASSIGNED PADec 13, 2006abuse@rt.ru
via RU-RTK-20050601
└ 86.102.91.80/2816POL-GREVIS-NETCollection Agency Grevis, LTDASSIGNED PASep 21, 2009abuse@rt.ru
via RU-RTK-20050601
└ 86.102.91.96/2816POL-PFKBVOSTOCHNY-NETKB Vostochny, Primorsky BranchASSIGNED PAApr 30, 2008abuse@rt.ru
via RU-RTK-20050601
└ 86.102.91.112/2816POL-SUMMITBANK-NETSummit BankASSIGNED PADec 21, 2006abuse@rt.ru
via RU-RTK-20050601
└ 86.102.91.160/2816POL-BRIGSTAR-NETBrig-StarASSIGNED PAJan 24, 2007abuse@rt.ru
via RU-RTK-20050601
└ 86.102.91.208/2816POL-KULIKIA-NETIrina Kulik Private EstablishmentASSIGNED PAJan 29, 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.

Composition

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

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Business12850%8
Residential12850%5

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

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