Data as of Nov 13, 2026

217.19.112.0/22

5 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
No RPKI
Announced by
Type
Business

Residential-proxy exits

Proxy exits
5
0.49% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
25
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.3K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
217.19.115.0/2403
217.19.112.0/2402

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • FlashProxy
  • GSocks
  • GonzoProxy
  • IPFly
  • Infatica
  • LightningProxies
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
217.19.112.0/23
since Sep 2019
AS3216Business2PJSC "Vimpelcom"
217.19.114.0/24
since Sep 2019
AS3216BusinessPJSC "Vimpelcom"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.19.112.0/204,096RU-SOVINTEL-20030123PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAJan 23, 2003abuse-b2b@beeline.ru
└ 217.19.112.0/221,024RU-BeeLine-UICARD-b2b-clients-NET111250 Russia SOVINTEL/EDN et UralInterCardASSIGNED PAJan 23, 2003abuse-b2b@beeline.ru
via RU-SOVINTEL-20030123

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

Who has announced 217.19.112.0/20

217.19.112.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Oct 2019 · 7.1 yr
Origin networks
2
Last change of origin
Oct 2019
Recorded history

History

Handoffs
1