Data as of Nov 20, 2026

31.169.17.0/24

4 residential-proxy exits · 30 days

JSC Kazakhtelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business
98% of it

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
16
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

111 observations

Proxy providers listing exits

  • 9HTTP
  • BestProxy
  • FastProxy
  • GEEKPROXY_FLEX
  • KocerRoxy
  • LemonBright
  • NSocks
  • PROXY_CC
  • Proxiware
  • Proxy302
  • RainProxy
  • Shifter
  • Smartproxy
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
31.169.0.0/19
since Jan 2016
AS9198Residential1,264
19 always on
JSC Kazakhtelecom

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
31.169.0.0/198,192KZ-KAZAKTELECOM-20110328JSC Kazakhtelecom (ORG-KDNA1-RIPE) · KZALLOCATED PAMar 28, 2011abuse@telecom.kz
└ 31.169.17.0/304OTDELZEMELNYHOTNASHENYGU Rayonny Otdel Zemelnyh OtnashenyASSIGNED PASep 19, 2016abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.4/304OTDELVETERYNARYGU Karmakshynsky Rayonny Otdel VeterynaryASSIGNED PASep 19, 2016abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.8/304SCHOLA19KyzylordaASSIGNED PAJan 6, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.12/304APPAKIMATunknownASSIGNED PAMay 14, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.16/298CENTROBSLUZHYVANYANASELENYAunknownASSIGNED PAMar 16, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.24/304MIKRK_GCHPunknownASSIGNED PAJun 10, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.28/304MIKRK_GCHPunknownASSIGNED PAJun 10, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.32/304MIKRK_GCHPunknownASSIGNED PAJun 10, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.36/304SCHOOL48KyzylordaASSIGNED PAJan 14, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.40/304SPORTSCHOOL17KyzylordaASSIGNED PAJan 30, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.44/304MIKRK_GCHPunknownASSIGNED PAJun 10, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.48/304MTSunknownASSIGNED PAJun 23, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.52/304SCHOLA17KyzylordaASSIGNED PASep 17, 2025abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.56/304ASTICOMPANYKyzylordaASSIGNED PAAug 1, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.60/304MIKRK_GCHPunknownASSIGNED PAJun 10, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.64/304MIKRK_GCHPunknownASSIGNED PAJun 10, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.68/304MIKRK_GCHPunknownASSIGNED PAJun 10, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.72/304MIKRK_GCHPunknownASSIGNED PAJun 10, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.76/304MIKRK_GCHPunknownASSIGNED PAJun 10, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.80/304MIKRK_GCHPunknownASSIGNED PAJun 10, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.84/304MIKRK_GCHPunknownASSIGNED PAJun 10, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.88/304MIKRK_GCHPunknownASSIGNED PAJun 10, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.92/304MIKRK_GCHPunknownASSIGNED PAJun 10, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.96/2732KYZYLOZEKApparat Akimat KyzylozekASSIGNED PAJun 10, 2014abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.128/2732APPAKIMATApparat AkimatASSIGNED PAJul 1, 2014abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.160/304ARALVETSTANCIAKyzylordaASSIGNED PAFeb 22, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.164/304ARALVETSTANCIAKyzylordaASSIGNED PAFeb 22, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.168/304ARALVETSTANCIAKyzylordaASSIGNED PAFeb 22, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.172/304ARALVETSTANCIAKyzylordaASSIGNED PAFeb 22, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.176/304SCHOLA170KyzylordaASSIGNED PAFeb 22, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.180/304SCHOLA165KyzylordaASSIGNED PAFeb 22, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.184/304ARALVETSTANCIAKyzylordaASSIGNED PAFeb 22, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.188/304ARALVETSTANCIAKyzylordaASSIGNED PAFeb 27, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.196/304DOMKULTURAABAYKyzylordaASSIGNED PAMay 18, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.200/304KAZAKHSKAYASCHOOL157KyzylordaASSIGNED PAOct 24, 2023abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.204/304KAZTRANSGAZAYMAKunknownASSIGNED PAJun 9, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.208/304VETCONTROLunknownASSIGNED PAMar 26, 2026abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.212/304IPAIGOZHAEVAIP Aigozhaeva YilviraASSIGNED PAJul 5, 2018abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.216/304GENPROSASTKyzylorda cityASSIGNED PAApr 18, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.220/304ZHOSSPORTITURIZMAKyzylordaASSIGNED PAApr 25, 2024abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.224/304CENTROBSLUZHYVANYANASELENYAunknownASSIGNED PAMar 31, 2016abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.228/304MLOMBARDThe company with limited liability <MKLOMBARD>ASSIGNED PAAug 21, 2014abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.232/304MLOMBARDThe company with limited liability <MKLOMBARD>ASSIGNED PAAug 21, 2014abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.236/304MLOMBARDThe company with limited liability <MKLOMBARD>ASSIGNED PAAug 21, 2014abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.240/304MLOMBARDThe company with limited liability <MKLOMBARD>ASSIGNED PAAug 21, 2014abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.244/304MLOMBARDThe company with limited liability <MKLOMBARD>ASSIGNED PAAug 21, 2014abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.248/304MLOMBARDThe company with limited liability <MKLOMBARD>ASSIGNED PAAug 21, 2014abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328
└ 31.169.17.252/304MLOMBARDThe company with limited liability <MKLOMBARD>ASSIGNED PAAug 21, 2014abuse@telecom.kz
via KZ-KAZAKTELECOM-20110328

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Business25298%48
Residential41.6%1

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Oct 2011
Current origin since
Jun 2014 · 12 yr
Origin networks
2
Last change of origin
Jun 2014
Recorded history

History

Handoffs
1