Q-shu Tele Communications

BGP inherited
Cluster stats
Netblocks8
All fragments 339 blocks across 144 clusters
Cluster ID207725502
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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

4 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-13

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
101.203.104.24/32 Q-shu Tele Communications PEERINGDB ASSIGNED ● high
103.246.232.178/32 Q-shu Tele Communications PEERINGDB ASSIGNED ● high
210.173.184.115/32 Q-shu Tele Communications PEERINGDB ASSIGNED ● high
218.100.9.157/32 Q-shu Tele Communications PEERINGDB ASSIGNED ● high
2001:7fa:7:2:0:1:8092:1/128 Q-shu Tele Communications PEERINGDB ASSIGNED ● high
2001:de8:8:6:0:1:8092:1/128 Q-shu Tele Communications PEERINGDB ASSIGNED ● high
2001:de8:c:2:0:1:8092:1/128 Q-shu Tele Communications PEERINGDB ASSIGNED ● high
2001:de8:c:4:0:1:8092:1/128 Q-shu Tele Communications PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS18092