Kaztranscom
Cluster stats
Netblocks11
Cluster ID192823026
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
178.18.225.136/32 Kaztranscom PEERINGDB ASSIGNED ● high
185.232.60.150/32 Kaztranscom PEERINGDB ASSIGNED ● high
185.232.60.160/32 Kaztranscom PEERINGDB ASSIGNED ● high
185.232.60.161/32 Kaztranscom PEERINGDB ASSIGNED ● high
195.2.230.204/32 Kaztranscom PEERINGDB ASSIGNED ● high
195.12.116.11/32 Kaztranscom PEERINGDB ASSIGNED ● high
2a03:5f80:4::225:136/128 Kaztranscom PEERINGDB ASSIGNED ● high
2a0d:e180::60:150/128 Kaztranscom PEERINGDB ASSIGNED ● high
2a0d:e180::60:160/128 Kaztranscom PEERINGDB ASSIGNED ● high
2a0d:e180::60:161/128 Kaztranscom PEERINGDB ASSIGNED ● high
188.128.21.168/30 KazTransCom RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: F how networks compare →
18.2% of checked blocks have valid RPKI ROA coverage (2 of 11)
No discrepancies found among checked blocks.

NIC Handles

AS35104 DUMY-RIPE DUMY-RIPE ROSTELECOM-MNT