Data as of Nov 22, 2026

217.116.152.0/21

15 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
15
0.73% of its addresses · 30 days
Always-on exits
2
13% of its exits
Spread
3 of 8
/24s with at least one exit
Providers
70
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

7.7K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
217.116.154.0/2416
217.116.152.0/2414
217.116.153.0/2405

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • AETHYN_ELITE
  • Ake.net
  • BUYPERSONALPROXY
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HASDATA
  • HideProxy
  • IPFly
  • IPMUSK
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSTPROXY_LITE
  • NSTPROXY_PRIME
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • PROXIWARE_ECO
  • PROXYLANE
  • PROXYSAVER
  • PROXYSCRAPE
  • Proxies.fo
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • Shifter
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_X
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
217.116.128.0/19
since Nov 2015
AS12389Residential15
2 always on
PJSC Rostelecom
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
217.116.152.0/22
since Feb 2016
AS12389Residential15
2 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.116.128.0/198,192RU-RTK-20010206PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAMar 21, 2002abuse@rt.ru
└ 217.116.152.0/221,024Yrg-KuzbassnetYurga branchASSIGNED PA—abuse@rt.ru
via RU-RTK-20010206
└ 217.116.156.0/221,024Tpk-KuzbassnetTopky branchASSIGNED PA—abuse@rt.ru
via RU-RTK-20010206

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
Nov 2015
Current origin since
Nov 2015 · 11 yr
Origin networks
1