Data as of Nov 18, 2026

195.218.149.0/24

2 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
31
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

697 observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • Byteful
  • CatProxies
  • Datarama
  • EnigmaProxy
  • Evomi
  • GSocks
  • GhostConnect
  • HPROXY
  • HideProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LOKIPROXY
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_BASIC
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
195.218.128.0/17
since May 2005
AS3216Residential205
27 always on
PJSC "Vimpelcom"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
195.218.128.0/1732,768RU-SOVINTEL-961224PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PA—abuse-b2b@beeline.ru
└ 195.218.149.0/24256SOVINTEL-Interface-and-routedSOVINTELASSIGNED PAApr 4, 2005abuse-b2b@beeline.ru
via RU-SOVINTEL-961224

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

195.218.144.0/20

Routing history

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