Data as of Nov 20, 2026

176.15.240.0/23

2 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
this exact prefix
No RPKI
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address
Recent change
New origin Sep 28, 2026
its first announcement on record

Residential-proxy exits

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

Exits seen per day

2 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
176.15.240.0/2401
176.15.241.0/2401

Proxy providers listing exits

  • ASHBURNPROXIES
  • PuraRoute

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
176.14.0.0/15
since May 2011
AS8402Residential23,303
11 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
176.14.0.0/15131,072RU-CORBINA-20110518PJSC "Vimpelcom" (ORG-CTAM1-RIPE) · RUALLOCATED PAMay 18, 2011abuse-b2b@beeline.ru
└ 176.15.192.0/1816,384BEELINE-BROADBANDDynamic IP Pool for Broadband CustomersASSIGNED PAAug 2, 2024abuse-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

Summary

Routing history

Pattern
Stable
First seen
Sep 28, 2026
Current origin since
Sep 28, 2026 · 2 mo
Origin networks
1