Data as of Nov 15, 2026

213.221.63.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
19
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

347 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • FlashProxy
  • GonzoProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.221.0.0/18
since May 2005
AS3216Residential139
16 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.221.0.0/1816,384RU-SOVINTEL-19991230PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PADec 14, 2001abuse-b2b@beeline.ru
└ 213.221.63.0/24256SOVINTEL-Interface-NetworkSOVINTEL Interface addressASSIGNED PAOct 22, 2002abuse-b2b@beeline.ru
via RU-SOVINTEL-19991230

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.221.48.0/20

Routing history

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