Data as of Nov 21, 2026

194.67.63.200/30

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
2
50% of its addresses · listed by providers
Providers
32
selling exits here

Proxy providers listing exits

  • 9Proxy
  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • BottingTools
  • Byteful
  • CYBERYOZH
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonode
  • HASDATA
  • IPPeak
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NodeProxy
  • PROXYSCRAPE
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyGeo
  • ProxyStyler
  • Proxyma
  • RainProxy
  • RealProxy
  • ResiProxies
  • SOTAPROXY
  • Shifter

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
194.67.0.0/18
since May 2005
AS3216Residential130
13 always on
PJSC "Vimpelcom"

Registrations in this block

The registry's network records over this block, widest first, each 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.63.200/304RU-SOVINTEL-MRM-GRChC-FGuP-NET183032 Russia MurmanskASSIGNED PAMar 26, 2021abuse-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

194.67.62.0/23

Routing history

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