Data as of Nov 13, 2026

176.50.237.0/24

14 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
14
5.5% of its addresses · 30 days
Providers
34
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

286 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • GSocks
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • KindProxy
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
176.50.192.0/18
since Jan 2015
AS12389Residential2,008
20 always on
PJSC Rostelecom
176.50.0.0/16
since Oct 2017
AS12389Residential13,180
21 always on
PJSC Rostelecom
176.48.0.0/14
since Aug 2016
AS12389Residential31,698
22 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
176.48.0.0/14262,144RU-RTK-20110523PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAMay 23, 2011abuse@rt.ru
└ 176.50.224.0/198,192WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAFeb 13, 2012abuse@rt.ru
via RU-RTK-20110523

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

176.50.224.0/20

Routing history

Pattern
Stable
First seen
Feb 2012
Current origin since
Oct 2020 · 6.0 yr
Origin networks
2
Last change of origin
Jan 2018
Recorded history

History

Handoffs
1