Data as of Nov 15, 2026

81.9.103.0/24

1 residential-proxy exit · 30 days

PJSC 'Vimpelcom'

Announcement
this exact prefix
No RPKI
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
1
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

2 observations

Proxy providers listing exits

  • NovaProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.9.96.0/20
since May 2005
AS20597Residential4
1 always on
PJSC "Vimpelcom"
via now PAO Vimpelcom - formely ZAO "ELTEL"
81.9.0.0/17
since Sep 2025
AS3216Residential4,233
162 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
81.9.0.0/1732,768RU-SOVINTEL-20020123PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAJan 23, 2002abuse-b2b@beeline.ru
└ 81.9.96.0/204,096RU-BeeLine-NETnow PAO Vimpelcom - formely ZAO "ELTEL" (ORG-EA40-RIPE) · RULIR-PARTITIONED PAJul 5, 2012abuse-b2b@beeline.ru
└ 81.9.103.0/24256RU-Bee-Line-B2B-FTTB-clients-NET111250 Russia SOVINTEL/EDN et ELTELASSIGNED PAOct 8, 2021abuse-b2b@beeline.ru
via RU-BeeLine-NET

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
Oct 2021
Current origin since
Oct 2021 · 5.1 yr
Origin networks
1