Data as of Nov 14, 2026

83.102.160.0/24

1 residential-proxy exit · 30 days

PJSC 'Vimpelcom'

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
98% of it

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
19
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

350 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • FlashProxy
  • GonzoProxy
  • IPOasis
  • Infatica
  • LightningProxies
  • NodeMaven
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
83.102.128.0/17
since May 2005
AS8402Residential25
3 always on
PJSC "Vimpelcom"

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
83.102.128.0/1732,768RU-CORBINA-20040302PJSC "Vimpelcom" (ORG-CTAM1-RIPE) · RUALLOCATED PAMar 2, 2004abuse-b2b@beeline.ru
└ 83.102.160.160/304MikrolanVlgOOO Mikrolan VLGASSIGNED PAAug 30, 2022abuse-b2b@beeline.ru
via RU-CORBINA-20040302

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
Residential25298%2
Business41.6%1

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Feb 2013
Current origin since
Feb 2013 · 14 yr
Origin networks
1