Data as of Nov 14, 2026

81.211.107.0/24

2 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
No RPKI
Announced by
Type
Business
63% of it

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
9
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

13 observations
  • Residential
  • Business

Proxy providers listing exits

  • BirdProxies
  • GSocks
  • Infatica
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxy-Seller
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.211.0.0/17
since May 2005
AS3216Residential383
46 always on
PJSC "Vimpelcom"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
81.211.0.0/1732,768RU-SOVINTEL-20021104PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PANov 4, 2002abuse-b2b@beeline.ru
└ 81.211.107.0 - 81.211.107.9596SOVINTELInterface & routed networkASSIGNED PAMar 15, 2006abuse-b2b@beeline.ru
via RU-SOVINTEL-20021104
└ 81.211.107.192/2732RU-SOVINTEL-SPB-VELMOL-NETVELMOLASSIGNED PAMar 6, 2017abuse-b2b@beeline.ru
via RU-SOVINTEL-20021104
└ 81.211.107.224/2732SOVINTEL-OSTunknownASSIGNED PANov 22, 2004abuse-b2b@beeline.ru
via RU-SOVINTEL-20021104

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Business16063%3
Residential9638%1

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

81.211.96.0/19

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1