Data as of Nov 17, 2026

212.44.134.0/24

3 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
21
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

258 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FlashProxy
  • GonzoProxy
  • HydraProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.44.128.0/198,192RU-SOVINTEL-980423PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PADec 17, 2001abuse-b2b@beeline.ru
└ 212.44.134.0/25128RU-SOVINTEL-OREL-FTTB-Middleware-NET111250 Russia Moscow SOVINTEL/EDNASSIGNED PADec 29, 2010abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.134.128/25128RU-SOVINTEL-EDN-Static-IP-pool-NET111250 Russia Moscow SOVINTEL/EDNASSIGNED PAFeb 9, 2011abuse-b2b@beeline.ru
via RU-SOVINTEL-980423

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 212.44.128.0/19

212.44.128.0/19

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1