Data as of Nov 12, 2026

176.14.71.0/24

15 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
No RPKI
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
15
5.9% of its addresses · 30 days
Providers
35
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

188 observations

Proxy providers listing exits

  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Byteful
  • CatProxies
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • GSocks
  • Geonode
  • GloryCloud
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LudaxProxy
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • ResiProxies
  • Shifter
  • VantageProxies
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
176.14.0.0/15
since May 2011
AS8402Residential22,427
4 always on
PJSC "Vimpelcom"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
176.14.0.0/15131,072RU-CORBINA-20110518PJSC "Vimpelcom" (ORG-CTAM1-RIPE) · RUALLOCATED PAMay 18, 2011abuse-b2b@beeline.ru
└ 176.14.0.0/1665,536BEELINE-BROADBANDDynamic IP Pool for Broadband CustomersASSIGNED PAOct 17, 2011abuse-b2b@beeline.ru
via RU-CORBINA-20110518

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

176.14.0.0/16

Routing history

Pattern
Stable
First seen
Aug 2025
Current origin since
Aug 2025 · 1.2 yr
Origin networks
1