Data as of Nov 10, 2026

212.44.136.0/24

3 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
No RPKI
Announced by
Type
Residential
72% of it

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
27
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

268 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FloppyData
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VibeProxies
  • 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.136.0 - 212.44.136.175176RU-BeeLine-B2B-client-IP-pool-NET111250 Russia SOVINTEL/EDN et SovAm TeleportASSIGNED PAJan 27, 2025abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.136.176/298RU-SOVINTEL-MSK-GorProekt-NET105047 Russia Moscow, ZC- 9894273ASSIGNED PAOct 5, 2015abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.136.192/2816RU-SOVINTEL-MSK-Sofcom-NET127247 Russia Moscow, ZC-7910836ASSIGNED PAApr 30, 2014abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.136.208/298RU-BeeLine-MSK-SyMTeLeKoM-NET121099 Russia Moscow, ZC-21813999ASSIGNED PAFeb 10, 2026abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.136.216/298SOVINTEL-Debevoise-Plimpton-NETMoscow RussiaASSIGNED PAFeb 25, 2003abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.136.224/298RU-SOVINTEL-MSK-Prizyv-factory-NET119334 Russia, Moscow, ZC-4132250ASSIGNED PAJun 11, 2010abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.136.232/298RU-SOVINTEL-MSK-LOXITAN-RUS-NET111315 Russia, Moscow, KL-1705276ASSIGNED PAJun 22, 2009abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.136.240/298RU-SOVINTEL-MSK-Gerkon-AV-NET143033 Russia Moscow Odincovo, ZC-6405549ASSIGNED PAApr 29, 2013abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.136.248/298RU-SOVINTEL-B2B-MSK-KSB-NET121099 Russia Moscow, ZC- 20105198ASSIGNED PAOct 2, 2012abuse-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.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Residential18472%2
Business7228%8

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