Data as of Nov 20, 2026

87.224.220.0/23

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.39% of its addresses · 30 days
Always-on exits
1
50% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
20
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

2.5K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
87.224.221.0/2411
87.224.220.0/2401

Proxy providers listing exits

  • AETHYN_ELITE
  • BirdProxies
  • Byteful
  • CYBERYOZH
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • HASDATA
  • Infatica
  • MangoProxy
  • NodeProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxyma
  • SOTAPROXY
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.224.128.0/17
since Jul 2005
AS35154Residential422
62 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.224.128.0 - 87.225.127.25565,536RU-RTK-20050614PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 18, 2013abuse@rt.ru
└ 87.224.220.0/24256KABINETTeleset-Servis Ltd.ASSIGNED PANov 16, 2006abuse@rt.ru
via RU-RTK-20050614
└ 87.224.221.0/24256KABINETTeleset-Servis Ltd.ASSIGNED PANov 16, 2006abuse@rt.ru
via RU-RTK-20050614

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
Jun 2020
Current origin since
Sep 2024 · 2.1 yr
Origin networks
1