Data as of Nov 14, 2026

194.67.46.0/23

6 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
6
1.2% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
29
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

966 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
194.67.46.0/2405
194.67.47.0/2401

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
194.67.0.0/18
since May 2005
AS3216Residential127
12 always on
PJSC "Vimpelcom"

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
194.67.0.0/1816,384RU-SOVINTEL-940418PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PA—abuse-b2b@beeline.ru
└ 194.67.46.0/24256SovintelSovintel routed and interface networkASSIGNED PAApr 3, 2006abuse-b2b@beeline.ru
via RU-SOVINTEL-940418
└ 194.67.47.0/24256GoldenTelecomInterface & routed networkASSIGNED PAApr 3, 2006abuse-b2b@beeline.ru
via RU-SOVINTEL-940418

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Mar 2006
Current origin since
Mar 2006 · 21 yr
Origin networks
1