Data as of Nov 20, 2026

87.225.75.0/26

No anonymizer space · no proxy exits in 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
62
97% of its addresses · listed by providers
Always-on exits
37
60% of its exits
Providers
69
selling exits here

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • AETHYN_ELITE
  • Ake.net
  • AnyIP
  • BUYPERSONALPROXY
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlashProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonode
  • GhostConnect
  • GonzoProxy
  • HASDATA
  • HPROXY
  • HideProxy
  • IPFly
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYLANE
  • PROXYON
  • PROXYSAVER
  • PROXYSCRAPE
  • PYPROXY
  • PrivateProxy
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.225.64.0/18
since Jul 2006
AS34584Residential2,758
90 always on
PJSC Rostelecom
87.225.0.0/17
since Feb 2007
AS34584Residential5,591
99 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.224.128.0 - 87.225.127.25565,536RU-RTK-20050614PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 18, 2013abuse@rt.ru
└ 87.225.75.0/2664KHT-XDSLstatic and PPPoE xDSL links in Komsomolsk-at-Amur town , ATS-530 nodeASSIGNED PADec 28, 2007abuse@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

87.225.72.0/21

Routing history

Pattern
Stable
First seen
Mar 2010
Current origin since
Mar 2010 · 17 yr
Origin networks
1