Data as of Nov 12, 2026

128.0.26.0/24

17 residential-proxy exits · 30 days

Sibirskie Seti Ltd. · space held by Norilsk-Telecom JSC

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

Residential-proxy exits

Proxy exits
17
6.6% of its addresses · 30 days
Always-on exits
1
5.9% of its exits
Providers
44
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

4.1K observations

Proxy providers listing exits

  • 2Captcha
  • 911Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • MagneticProxy
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxyma
  • Q2IP
  • RainProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
128.0.24.0/212,048RU-NORCOM-20120914Norilsk-Telecom JSC (ORG-NL23-RIPE) · RUALLOCATED PAMar 17, 2020abuse@sibset-team.ru
└ 128.0.26.0/24256RU-ISP-SIBSET-BARN-2Sibirskie Seti AltayASSIGNED PAOct 7, 2021abuse@sibset-team.ru
via RU-NORCOM-20120914

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

Who has announced 128.0.24.0/21

128.0.24.0/21

Routing history

Pattern
Stable
First seen
Sep 2012
Current origin since
Sep 2012 · 14 yr
Origin networks
1