Data as of Nov 18, 2026

79.104.220.0/23

1 residential-proxy exit · 30 days

PJSC 'Vimpelcom'

Announcement
No RPKI
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
1
0.20% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
7
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

11 observations

Proxy providers listing exits

  • Byteful
  • Infatica
  • LightningProxies
  • PROXYSCRAPE
  • Proxy-Seller
  • Proxyma
  • Shifter

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
79.104.192.0/19
since Jan 2009
AS3216Residential64
6 always on
PJSC "Vimpelcom"
More specific

Announcements inside

PrefixOriginTypeHolderRPKI
79.104.220.0/24
since Nov 2021
AS3216ResidentialPJSC "Vimpelcom"

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.220.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

79.104.216.0/21

Routing history

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