Data as of Nov 17, 2026

92.126.240.0/20

32 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
32
0.78% of its addresses · 30 days
Always-on exits
4
13% of its exits
Spread
13 of 16
/24s with at least one exit
Providers
81
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

19K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • AETHYN_ELITE
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • MarsProxies
  • Maskify
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • SwiftProxy
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
92.126.224.0/19
since Sep 2015
AS12389Residential40
4 always on
PJSC Rostelecom
92.124.0.0/14
since Aug 2016
AS12389Residential21,386
1,263 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
92.124.0.0/14262,144RU-RTK-20071116PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAMay 22, 2008abuse@rt.ru
└ 92.126.224.0/198,192RU-SIBNETunknownLIR-PARTITIONED PAJul 31, 2008abuse@rt.ru
via RU-RTK-20071116
└ 92.126.240.0 - 92.126.251.2553,072WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PANov 20, 2008abuse@rt.ru
via RU-SIBNET
└ 92.126.252.0/221,024WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PANov 20, 2008abuse@rt.ru
via RU-SIBNET

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
Mar 2025
Current origin since
Mar 2025 · 1.6 yr
Origin networks
1