Data as of Nov 14, 2026

213.33.136.0/22

14 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
14
1.4% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
11
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

271 observations

/24s with the most always-on exits

Proxy providers listing exits

  • EnigmaProxy
  • IPFly
  • NSocks
  • NovaProxy
  • Proxiware
  • ProxyEmpire
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.33.128.0/17
since May 2005
AS3216Residential322
41 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
213.33.128.0/1732,768RU-SOVINTEL-20010111PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PADec 14, 2001abuse-b2b@beeline.ru
└ 213.33.136.0/221,024RU-BeeLine-B2B-179-WiFi-Hot-Spot-NET111250 Russia SOVINTEL/EDNASSIGNED PAAug 11, 2025abuse-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

Summary

Routing history

Pattern
Stable
First seen
Oct 2025
Current origin since
Oct 2025 · 1.1 yr
Origin networks
1