Data as of Nov 19, 2026

213.33.252.64/28

1 residential-proxy exit · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
1
6.3% of its addresses · 30 days
Always-on exits
1
100% of its exits
Providers
20
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

3.8K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FlashProxy
  • FloppyData
  • GonzoProxy
  • Infatica
  • LightningProxies
  • NodeMaven
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.33.128.0/17
since May 2005
AS3216Residential334
41 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.252.64/2816SOVINTEL-MULTIMOTORSunknownASSIGNED PAApr 6, 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.240.0/20

Routing history

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