Data as of Nov 22, 2026

79.104.54.0/24

3 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
40
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

383 observations

Proxy providers listing exits

  • AETHYN_BASIC
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • GEEKPROXY_TURBO
  • GSocks
  • GloryCloud
  • GonzoProxy
  • HASDATA
  • IPMUSK
  • IPRoyal
  • Infatica
  • KindProxy
  • Kookey
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • RapidProxy
  • SOTAPROXY
  • Shifter
  • SwiftProxy
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
79.104.0.0/1665,536RU-SOVINTEL-20071120PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PANov 20, 2007abuse-b2b@beeline.ru
└ 79.104.54.0/24256RU-SOVINTEL-p2p-and-Static-lients-IP-Pool-NET111250 Russia SOVINTEL/EDNASSIGNED PADec 13, 2012abuse-b2b@beeline.ru
via RU-SOVINTEL-20071120

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

Who has announced 79.104.0.0/17

79.104.0.0/17

Routing history

Pattern
Stable
First seen
Jan 2009
Current origin since
Jan 2009 · 18 yr
Origin networks
1