Data as of Nov 10, 2026

87.103.172.0/22

71 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
71
6.9% of its addresses · 30 days
Always-on exits
8
11% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
78
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

29K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
87.103.172.0/24421
87.103.173.0/24419
87.103.175.0/24018
87.103.174.0/24013

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MarsProxies
  • Maskify
  • NSocks
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYWING_BASIC
  • PrivateByte
  • ProxiesVision
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RolaProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • TrueProxies
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.103.128.0/17
since Oct 2018
AS12389Residential596
85 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.103.128.0/1732,768RU-RTK-20051020PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAOct 20, 2005abuse@rt.ru
└ 87.103.172.0/221,024WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAMay 4, 2006abuse@rt.ru
via RU-RTK-20051020

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
May 2006
Current origin since
Jul 2015 · 11 yr
Origin networks
2
Last change of origin
Jul 2015
Recorded history

History

Handoffs
1