Data as of Nov 11, 2026

92.126.152.0/22

8 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
8
0.78% of its addresses · 30 days
Always-on exits
1
13% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
35
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

3.0K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
92.126.152.0/2414
92.126.154.0/2403
92.126.153.0/2401

Proxy providers listing exits

  • 2Captcha
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FlexyProxies
  • GSocks
  • Geonode
  • GonzoProxy
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
92.124.0.0/14
since Aug 2016
AS12389Residential21,093
1,249 always on
PJSC Rostelecom

Registrations in this block

The registry's network records over this block, widest first, each 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.152.0/221,024WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAFeb 1, 2011abuse@rt.ru
via RU-RTK-20071116

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

92.126.128.0/19

Routing history

Pattern
Stable
First seen
Mar 2015
Current origin since
Mar 2015 · 12 yr
Origin networks
1