Data as of Nov 13, 2026

92.126.210.0/24

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
3.1% of its addresses · 30 days
Providers
33
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.6K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlexyProxies
  • GSocks
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
92.124.0.0/14
since Aug 2016
AS12389Residential21,168
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.192.0/198,192RU-SIBNETunknownLIR-PARTITIONED PAJul 31, 2008abuse@rt.ru
via RU-RTK-20071116
└ 92.126.208.0/204,096WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 2, 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.192.0/19

Routing history

Pattern
Stable
First seen
Sep 2008
Current origin since
Dec 2015 · 11 yr
Origin networks
2
Last change of origin
Dec 2015
Recorded history

History

Handoffs
1