Data as of Nov 22, 2026

194.186.28.0/23

3 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
3
0.59% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
37
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

820 observations

Proxy providers listing exits

  • 2Captcha
  • AETHYN_ELITE
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
194.186.0.0/16
since May 2005
AS3216Residential883
92 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.186.0.0/1665,536RU-SOVINTEL-951205PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAJan 9, 2002abuse-b2b@beeline.ru
└ 194.186.28.0/24256RU-VIMPELCOM-SPB-p2p-NET-2Russia Saint-PetersBurg VIMPELCOM p2pASSIGNED PAMar 1, 2004abuse-b2b@beeline.ru
via RU-SOVINTEL-951205

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