Data as of Nov 20, 2026

87.117.173.0/24

2 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
2
0.78% of its addresses · 30 days
Providers
28
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

793 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • HASDATA
  • Infatica
  • MangoProxy
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • SOTAPROXY
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.117.160.0/19
since Oct 2018
AS12389Residential581
482 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
87.117.160.0/198,192RU-RTK-20050928PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PASep 28, 2005abuse@rt.ru
└ 87.117.160.0/204,096TELESET-KAZANTeleset LLCASSIGNED PAOct 23, 2026abuse@rt.ru
via RU-RTK-20050928

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
Dec 2006
Current origin since
Oct 2016 · 10 yr
Origin networks
2
Last change of origin
Oct 2016
Recorded history

History

Handoffs
1