Triple Zhi Network
Cluster stats
Netblocks10
All fragments 616 blocks across 44 clusters
Cluster ID193386838
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-06

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
43.254.83.26/32 Triple Zhi Network PEERINGDB ASSIGNED ● high
103.138.70.89/32 Triple Zhi Network PEERINGDB ASSIGNED ● high
103.225.173.253/32 Triple Zhi Network PEERINGDB ASSIGNED ● high
119.11.185.109/32 Triple Zhi Network PEERINGDB ASSIGNED ● high
123.108.10.182/32 Triple Zhi Network PEERINGDB ASSIGNED ● high
218.100.41.196/32 Triple Zhi Network PEERINGDB ASSIGNED ● high
218.100.72.58/32 Triple Zhi Network PEERINGDB ASSIGNED ● high
2001:7fa:2:5::2c6/128 Triple Zhi Network PEERINGDB ASSIGNED ● high
2001:df0:b1:100::72:58/128 Triple Zhi Network PEERINGDB ASSIGNED ● high
2400:9c80:0:173::150:551/128 Triple Zhi Network PEERINGDB ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: C how networks compare →
50.0% of checked blocks have valid RPKI ROA coverage (5 of 10)
No discrepancies found among checked blocks.

NIC Handles

AS150551