Data as of Nov 19, 2026

87.225.104.0/22

63 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
63
6.2% of its addresses · 30 days
Always-on exits
9
14% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
84
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

26K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
87.225.106.0/24415
87.225.105.0/24317
87.225.107.0/24117
87.225.104.0/24114

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_BASIC
  • AETHYN_ELITE
  • APROXY
  • ASHBURNPROXIES
  • Ake.net
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • CYBERYOZH
  • CliProxy
  • DataImpulse
  • Datarama
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HASDATA
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LUMIPROXY
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXIES.RIP
  • PROXYLANE
  • PROXYSCRAPE
  • PacketStream
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Shifter
  • Smartproxy
  • TORCHPROXIES_BASIC
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.225.64.0/18
since Jul 2006
AS34584Residential2,755
90 always on
PJSC Rostelecom
87.225.0.0/17
since Feb 2007
AS34584Residential5,571
99 always on
PJSC Rostelecom
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
87.225.107.0/24
since Nov 2016
AS12389Residential17
1 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.225.104.0/2664KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-490 nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.104.64/2664KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-490 nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.104.128/2816KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-932 nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.104.144/2816KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-499 nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.104.160/2816KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, HONET-61 nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.104.176/2816KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-497 nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.105.0/2664KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-297 nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.105.128/2664KHT-XDSLstatic and PPPoE xDSL links in Khabarovsk city, ATS-34 nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.107.0/25128KHT-XDSLstatic and PPPoE xDSL links in Komsomolsk-at-Amur town , central nodeASSIGNED PADec 29, 2007abuse@rt.ru
via RU-RTK-20050614
└ 87.225.107.128/2664KHT-XDSLstatic and PPPoE xDSL links in Okhotsk village, central nodeASSIGNED PADec 29, 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

Summary

Routing history

Pattern
Reactivated
First seen
Jun 2007
Current origin since
Jan 2024 · 2.8 yr
Origin networks
2
Last change of origin
Jan 2024
Recorded history

History

Handoffs
1