Data as of Nov 10, 2026

95.58.91.76/30

1 residential-proxy exit · 30 days

JSC Kazakhtelecom

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

Residential-proxy exits

Proxy exits
1
25% of its addresses · 30 days
Providers
33
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

277 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • BestProxy
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • GonzoProxy
  • Infatica
  • LUMIPROXY
  • LemonBright
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.56.0.0/14
since Oct 2008
AS9198Residential57,047
959 always on
JSC Kazakhtelecom

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.56.0.0/14262,144KZ-KAZAKTELECOM-20080923JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZALLOCATED PASep 23, 2008abuse@telecom.kz
└ 95.58.91.76/304KGU_YUNOSHESKII_KLUB_TIMIRYAZEVORC TimiryazevoASSIGNED PAMar 10, 2021abuse@telecom.kz
via KZ-KAZAKTELECOM-20080923

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

95.58.64.0/19

Routing history

Pattern
Stable
First seen
Apr 2009
Current origin since
Oct 2016 · 10 yr
Origin networks
1