On Q Communications
Cluster stats
Netblocks20
All fragments 36 blocks across 3 clusters
Cluster ID193383240
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

IP Ranges (20)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.127.173.66/32 On Q Communications PEERINGDB ASSIGNED ● high
103.26.68.172/32 On Q Communications PEERINGDB ASSIGNED ● high
103.26.70.52/32 On Q Communications PEERINGDB ASSIGNED ● high
103.26.71.109/32 On Q Communications PEERINGDB ASSIGNED ● high
103.136.103.47/32 On Q Communications PEERINGDB ASSIGNED ● high
202.77.88.142/32 On Q Communications PEERINGDB ASSIGNED ● high
202.77.90.81/32 On Q Communications PEERINGDB ASSIGNED ● high
218.100.52.96/32 On Q Communications PEERINGDB ASSIGNED ● high
218.100.76.5/32 On Q Communications PEERINGDB ASSIGNED ● high
218.100.78.54/32 On Q Communications PEERINGDB ASSIGNED ● high
2001:7fa:11:1:0:1daa:0:1/128 On Q Communications PEERINGDB ASSIGNED ● high
2001:7fa:11:2:0:1daa:0:1/128 On Q Communications PEERINGDB ASSIGNED ● high
2001:7fa:11:4:0:1daa:0:1/128 On Q Communications PEERINGDB ASSIGNED ● high
2001:de8:6::7594:1/128 On Q Communications PEERINGDB ASSIGNED ● high
2001:dea:0:10::ac/128 On Q Communications PEERINGDB ASSIGNED ● high
2001:dea:0:20::34/128 On Q Communications PEERINGDB ASSIGNED ● high
2001:dea:0:30::6d/128 On Q Communications PEERINGDB ASSIGNED ● high
2001:df0:680:4::2f/128 On Q Communications PEERINGDB ASSIGNED ● high
2001:df0:680:5::8d/128 On Q Communications PEERINGDB ASSIGNED ● high
2001:df0:680:6::51/128 On Q Communications PEERINGDB ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: B how networks compare →
80.0% of checked blocks have valid RPKI ROA coverage (16 of 20)
No discrepancies found among checked blocks.

NIC Handles

AS7594