Data as of Nov 18, 2026

31.31.223.0/24

1 residential-proxy exit · 30 days

JSC Kazteleport - subsidiary of Halyk Bank of Kazakhstan

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
10
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

87 observations

Proxy providers listing exits

  • 9HTTP
  • APROXY
  • BestProxy
  • LUMIPROXY
  • NSocks
  • Proxies.fo
  • RainProxy
  • Shifter
  • Smartproxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
31.31.216.0/21
since Feb 2019
AS197686Hosting11JSC Kazteleport - subsidiary of Halyk Bank of Kazakhstan

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.31.216.0/212,048KZ-KAZTELEPORT-20110321JSC Kazteleport - subsidiary of Halyk Bank of Kazakhstan (ORG-JKSO1-RIPE) · KZALLOCATED PAMar 21, 2011abuse@kazteleport.kz
└ 31.31.223.0/304INFRAKazteleport InfrastructureASSIGNED PAMar 10, 2016abuse@kazteleport.kz
via KZ-KAZTELEPORT-20110321
└ 31.31.223.4/304INFRAKazteleport InfrastructureASSIGNED PAMar 10, 2016abuse@kazteleport.kz
via KZ-KAZTELEPORT-20110321
└ 31.31.223.8/312INFRAKazteleport InfrastructureASSIGNED PAMar 10, 2016abuse@kazteleport.kz
via KZ-KAZTELEPORT-20110321
└ 31.31.223.10/312Kazteleport_InfrastructureunknownASSIGNED PAAug 23, 2024abuse@kazteleport.kz
via KZ-KAZTELEPORT-20110321
└ 31.31.223.14/312Kazteleport_InfrastructureunknownASSIGNED PAAug 23, 2024abuse@kazteleport.kz
via KZ-KAZTELEPORT-20110321
└ 31.31.223.18/312Kazteleport_InfrastructureunknownASSIGNED PAAug 23, 2024abuse@kazteleport.kz
via KZ-KAZTELEPORT-20110321
└ 31.31.223.24/298KASEunknownASSIGNED PADec 10, 2024abuse@kazteleport.kz
via KZ-KAZTELEPORT-20110321
└ 31.31.223.32/298TOO_ADAI_SOFTWARE_INETunknownASSIGNED PAApr 28, 2026abuse@kazteleport.kz
via KZ-KAZTELEPORT-20110321
└ 31.31.223.40/298MFO_Arnur_Credit_INETunknownASSIGNED PADec 27, 2024abuse@kazteleport.kz
via KZ-KAZTELEPORT-20110321
└ 31.31.223.48/2816InfoSoftProm_TOOunknownASSIGNED PAFeb 20, 2026abuse@kazteleport.kz
via KZ-KAZTELEPORT-20110321
└ 31.31.223.128/2732LLC_Jet_TechnologiesunknownASSIGNED PAJul 28, 2026abuse@kazteleport.kz
via KZ-KAZTELEPORT-20110321
└ 31.31.223.160/304Just_Back_Office_LLPunknownASSIGNED PAJun 26, 2026abuse@kazteleport.kz
via KZ-KAZTELEPORT-20110321

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
Stable
First seen
Aug 2011
Current origin since
Aug 2011 · 15 yr
Origin networks
1