Data as of Nov 18, 2026

195.46.162.0/24

21 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
21
8.2% of its addresses · 30 days
Always-on exits
4
19% of its exits
Providers
55
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

16K observations

Proxy providers listing exits

  • 2Captcha
  • 9HTTP
  • 9Proxy
  • Ake.net
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
195.46.160.0/19
since May 2005
AS3216Residential199
33 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
195.46.160.0/198,192RU-SOVINTEL-971016PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PA—abuse-b2b@beeline.ru
└ 195.46.162.0/24256FTTB-Cherepovets-NETFTTB Cherepovets ipv4 static poolsASSIGNED PANov 10, 2014abuse-b2b@beeline.ru
via RU-SOVINTEL-971016

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
Apr 2009
Current origin since
Dec 2025 · 12 mo
Origin networks
1