Data as of Nov 10, 2026

87.253.217.0/24

40 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
40
16% of its addresses · 30 days
Always-on exits
3
7.5% of its exits
Providers
46
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

4.6K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.253.192.0/19
since Feb 2024
AS12389Residential1,027
36 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
87.253.192.0/198,192RU-RTK-20051007PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAOct 7, 2005abuse@rt.ru
└ 87.253.208.0/204,096TCHERCOM-NETOJSC "Rostelecom" North-WestASSIGNED PASep 29, 2011abuse@rt.ru
via RU-RTK-20051007

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

87.253.216.0/23

Routing history

Pattern
Stable
First seen
Mar 2024
Current origin since
Mar 2024 · 2.7 yr
Origin networks
1