Data as of Nov 18, 2026

217.15.141.0/24

3 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
40
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

535 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • FlashProxy
  • GonzoProxy
  • IPOasis
  • Infatica
  • KindProxy
  • LightningProxies
  • MoMoProxy
  • NextProxy
  • NodeProxy
  • Novada
  • PROXYSCRAPE
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • Shifter
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
217.15.128.0/20
since May 2005
AS13118Residential522
14 always on
PJSC Rostelecom
217.15.128.0/19
since May 2005
AS13118Residential1,411
37 always on
PJSC Rostelecom

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
217.15.128.0/198,192RU-RTK-20000906PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAOct 22, 2002abuse@rt.ru
└ 217.15.140.0/23512MACROREGIONAL_CENTEROJSC Rostelecom, Yaroslavl branchASSIGNED PADec 20, 2024abuse@rt.ru
via RU-RTK-20000906

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
Feb 2016
Current origin since
Apr 2017 · 9.6 yr
Origin networks
1