Data as of Nov 16, 2026

79.104.223.0/24

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
1.2% of its addresses · 30 days
Providers
20
selling exits here
Oct 17, 2026 – Nov 14, 2026

Exits seen per day

1.2K observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GonzoProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
79.104.216.0/21
since Mar 2009
AS21483Residential6PJSC "Vimpelcom"
79.104.192.0/19
since Jan 2009
AS3216Residential60
5 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
79.104.0.0/1665,536RU-SOVINTEL-20071120PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PANov 20, 2007abuse-b2b@beeline.ru
└ 79.104.222.0/23512RU-SOVINTEL-KB-FTTB-Beeline-Clients-NETLLC "EDN Sovintel" Krasnoyarsk BranchASSIGNED PAMar 16, 2009abuse-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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Nov 2021
Current origin since
Nov 2021 · 5.0 yr
Origin networks
1