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

83.69.124.0/23

3 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
this exact prefix
No RPKI
Announced by
AS29125
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
3
0.59% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
29
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

2.5K observations

Proxy providers listing exits

  • 2Captcha
  • ASHBURNPROXIES
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EZProxies
  • FlashProxy
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • MangoProxy
  • MarsProxies
  • NodeMaven
  • PROXYSCRAPE
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
83.69.120.0/21
since Apr 2009
AS29125Residential7PJSC "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.69.96.0/198,192RU-SOVINTEL-20040526PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAMay 26, 2004abuse-b2b@beeline.ru
└ 83.69.124.0/23512TIC-FOR-ADSLunknownASSIGNED PAAug 18, 2005abuse-b2b@beeline.ru
via RU-SOVINTEL-20040526

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
Sep 2005
Current origin since
Aug 2006 · 20 yr
Origin networks
2
Last change of origin
Aug 2006
Recorded history

History

Handoffs
1