Data as of Nov 15, 2026

217.30.240.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

1.0K observations

Proxy providers listing exits

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

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
217.30.240.0/20
since Mar 2009
AS29125Residential5
2 always on
PJSC "Vimpelcom"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.30.240.0/204,096RU-SOVINTEL-20030604PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAJun 4, 2003abuse-b2b@beeline.ru
└ 217.30.240.0/24256TATINTELCOM-UNITELunknownASSIGNED PAJun 20, 2003abuse-b2b@beeline.ru
via RU-SOVINTEL-20030604

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

217.30.240.0/22

Routing history

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