Data as of Nov 16, 2026

95.30.104.0/21

2 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
No RPKI
Announced by
Type
Residential

Residential-proxy exits

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

Exits seen per day

77 observations

Proxy providers listing exits

  • BirdProxies
  • Byteful
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • IPFly
  • IPROCKET_BASIC
  • Infatica
  • MangoProxy
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.30.0.0/15
since Dec 2010
AS8402Residential2,523
282 always on
PJSC "Vimpelcom"
95.24.0.0/13
since Oct 2008
AS8402Residential200,815
11,562 always on
PJSC "Vimpelcom"
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
95.30.107.0/24
since Jul 2026
AS8402ResidentialPJSC "Vimpelcom"
95.30.109.0/24AS8402Residential1PJSC "Vimpelcom"
95.30.110.0/24AS8402ResidentialPJSC "Vimpelcom"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.24.0.0/13524,288RU-CORBINA-20081010PJSC "Vimpelcom" (ORG-CTAM1-RIPE) · RUALLOCATED PAOct 10, 2008abuse-b2b@beeline.ru
└ 95.24.0.0 - 95.30.255.255458,752BEELINE-BROADBANDDynamic IP Pool for broadband customersASSIGNED PAMay 12, 2010abuse-b2b@beeline.ru
via RU-CORBINA-20081010

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

95.30.0.0/16

Routing history

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