Data as of Nov 15, 2026

92.126.241.0/24

2 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Always-on exits
1
50% of its exits
Providers
21
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

3.2K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Byteful
  • Decodo
  • Geonode
  • IPFly
  • InfiniteProxies
  • Kookey
  • Novada
  • Oxylabs
  • PrivateProxy
  • PuraRoute
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
92.126.224.0/19
since Sep 2015
AS12389Residential40
3 always on
PJSC Rostelecom
92.124.0.0/14
since Aug 2016
AS12389Residential21,174
1,239 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.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

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.240.0/20

Routing history

Pattern
Stable
First seen
Mar 2025
Current origin since
Mar 2025 · 1.6 yr
Origin networks
1