Data as of Nov 15, 2026

92.62.68.0/24

22 residential-proxy exits · 30 days

CJSC Saima Telecom

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

Residential-proxy exits

Proxy exits
22
8.6% of its addresses · 30 days
Always-on exits
2
9.1% of its exits
Providers
60
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

4.9K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RoamProxy
  • SIMPLYNODE
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
92.62.64.0/21
since Aug 2016
AS29061Residential204
163 always on
CJSC Saima Telecom
92.62.64.0/20
since Mar 2008
AS29061Residential446
359 always on
CJSC Saima Telecom

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.62.64.0/204,096KG-SAIMANET-20080122CJSC Saima Telecom (ORG-ST1-RIPE) · KGALLOCATED PAJan 22, 2008marketing@saimanet.kg
└ 92.62.64.0/212,048SAIMANETftth pppoe customersASSIGNED PAAug 15, 2011marketing@saimanet.kg
via KG-SAIMANET-20080122

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
Rotating
First seen
Feb 2012
Current origin since
Feb 2025 · 1.7 yr
Origin networks
2
Last change of origin
Feb 2025
Recorded history

History

Handoffs
2