SGCC
Cluster stats
Netblocks11
All fragments 12 blocks across 2 clusters
Cluster ID192203031
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 5 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
103.16.103.66/32 SGCC PEERINGDB ASSIGNED ● high
103.231.152.222/32 SGCC PEERINGDB ASSIGNED ● high
119.11.185.9/32 SGCC PEERINGDB ASSIGNED ● high
119.11.185.10/32 SGCC PEERINGDB ASSIGNED ● high
119.11.187.79/32 SGCC PEERINGDB ASSIGNED ● high
119.11.193.9/32 SGCC PEERINGDB ASSIGNED ● high
2001:de8:12:100::103:66/128 SGCC PEERINGDB ASSIGNED ● high
2001:df5:b800:bb00:0:14:7168:1/128 SGCC PEERINGDB ASSIGNED ● high
2404:c8:0:a:0:14:7168:3/128 SGCC PEERINGDB ASSIGNED ● high
2404:c8:0:c:0:14:7168:1/128 SGCC PEERINGDB ASSIGNED ● high
86.64.11.176/29 SGCC RIPE ASSIGNED PA ● low

Network trust

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

NIC Handles

AS147168 DUMY-RIPE DUMY-RIPE LDCOM-MNT LDCOM-PRO-MNT