Data as of Nov 22, 2026

212.44.135.96/28

No anonymizer space · no proxy exits in 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
3
19% of its addresses · listed by providers
Always-on exits
1
33% of its exits
Providers
24
selling exits here

Proxy providers listing exits

  • BUYPERSONALPROXY
  • BirdProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GEEKPROXY_TURBO
  • HASDATA
  • HPROXY
  • HideProxy
  • InfiniteProxies
  • Kookey
  • LudaxProxy
  • NovaProxy
  • Novada
  • PROXIWARE_ECO
  • PROXYSAVER
  • PROXYSCRAPE
  • ProxyGeo
  • Proxyma
  • RainProxy
  • SPYDERPROXY_BASIC
  • Shifter
  • VantageProxies
  • ZENPROXY_LITE

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.135.96/2816RU-SOVINTEL-MSK-AMDtechnologies-NET127287 Russia Moscow, ZC-20799310ASSIGNED PAMar 5, 2007abuse-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