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

212.44.152.0/24

2 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
212.44.128.0/19
No RPKI
Announced by
AS3216
Type
Residential
53% of it

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
22
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

40 observations
  • Residential
  • Business

Proxy providers listing exits

  • BirdProxies
  • ByteProxies
  • Byteful
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPFly
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VitalData
  • 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.152.0/25128RU-SOVINTEL-EDN-Static-IP-Pool-NET111250 Russia SOVINTEL/EDNASSIGNED PAJun 27, 2011abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.152.128/298RU-SOVINTEL-MSK-B2B-clients-NET119019 Russia Moscow, ZC- 10031808ASSIGNED PAApr 16, 2015abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.152.144/298RU-SOVINTEL-MSK-aZaLyaDeKoR-NET114080 Russia Moscow, ZC- 13579250ASSIGNED PANov 13, 2010abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.152.152/298RU-BeeLine-MSK-Bank-BZHF-NET121357 Russia Moscow, ZC- 14204725ASSIGNED PAJul 4, 2012abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.152.160/298RU-SOVINTEL-MSK-BaLance-Insurance-NET125130 Russia Moscow, ZC-21201476ASSIGNED PAOct 30, 2003abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.152.168/298RU-SOVINTEL-MSK-Internet-Magazin-NET115230 Russia Moscow, ZC-5588064ASSIGNED PAMay 23, 2012abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.152.176/298RU-Beeline-MSK-INFINITY-TRADE-NET129329 Russia Moscow , ZC- 14853198ASSIGNED PAFeb 26, 2009abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.152.184/298RU-SOVINTEL-MSK-Kezer-Kompressoren-NET12504 Russia, Moscow, KL-1434399ASSIGNED PAJul 9, 2008abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.152.192/298RU-SOVINTEL-MSK-FaKToRKNyGa-NET121238 Russia Moscow, ZC- 12930060ASSIGNED PAJun 11, 2008abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.152.200/298SOVINTEL-BLACK-i-DECKER-NETMoscow RussiaASSIGNED PAOct 9, 2002abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.152.208/298RU-SOVINTEL-MSK-oPENSySTeMS-NET127051 Russia Moscow, ZC-5872917ASSIGNED PASep 25, 2012abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.152.216/298RU-SOVINTEL-MSK-Hotel-Management-NET125009 Russia Moscow, ZC- 13198734ASSIGNED PAApr 16, 2003abuse-b2b@beeline.ru
via RU-SOVINTEL-980423
└ 212.44.152.224/2732RU-SOVINTEL-MIAS-InMiner-UrO-RAN-NET456317 Russia Chelyabinsk, ZC- 9642113ASSIGNED PAJun 3, 2002abuse-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
Residential13653%2
Business12047%12

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
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