Data as of Nov 15, 2026

212.46.236.0/24

8 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
1
13% of its exits
Providers
44
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

2.1K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • StrikeProxy
  • TORCHPROXIES_X
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.46.192.0/1816,384RU-SOVINTEL-980821PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PA—abuse-b2b@beeline.ru
└ 212.46.236.128/2664RU-SOVINTEL-BRN-p2p-Static-IP-Pool-NET656000 Russia BarNaul SOVINTEL/EDNASSIGNED PAApr 10, 2012abuse-b2b@beeline.ru
via RU-SOVINTEL-980821

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.46.192.0/18

212.46.192.0/18

Routing history

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