Data as of Nov 17, 2026

213.33.239.0/24

1 residential-proxy exit · 30 days

PJSC 'Vimpelcom'

Announcement
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

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

Exits seen per day

55 observations

Proxy providers listing exits

  • EnigmaProxy
  • NovaProxy
  • Proxiware
  • ProxyEmpire
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.33.128.0/17
since May 2005
AS3216Residential316
40 always on
PJSC "Vimpelcom"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.33.128.0/1732,768RU-SOVINTEL-20010111PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PADec 14, 2001abuse-b2b@beeline.ru
└ 213.33.239.0/24256RU-VIMPELCOM-SPB-p2p-NET-15Russia Saint-PetersBurg VIMPELCOM p2pASSIGNED PAFeb 28, 2005abuse-b2b@beeline.ru
via RU-SOVINTEL-20010111

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

213.33.232.0/21

Routing history

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