Gigacom Systems
Cluster stats
Netblocks12
All fragments 18 blocks across 2 clusters
Cluster ID191871678
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 (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.28.19.217/32 Gigacom Systems PEERINGDB ASSIGNED ● high
31.28.19.223/32 Gigacom Systems PEERINGDB ASSIGNED ● high
178.18.224.34/32 Gigacom Systems PEERINGDB ASSIGNED ● high
178.18.227.103/32 Gigacom Systems PEERINGDB ASSIGNED ● high
185.0.13.41/32 Gigacom Systems PEERINGDB ASSIGNED ● high
185.1.153.226/32 Gigacom Systems PEERINGDB ASSIGNED ● high
195.208.209.77/32 Gigacom Systems PEERINGDB ASSIGNED ● high
195.208.209.197/32 Gigacom Systems PEERINGDB ASSIGNED ● high
2001:7f8:20:101::209:77/128 Gigacom Systems PEERINGDB ASSIGNED ● high
2001:7f8:20:101::209:197/128 Gigacom Systems PEERINGDB ASSIGNED ● high
2a03:5f80:4::224:34/128 Gigacom Systems PEERINGDB ASSIGNED ● high
2a03:5f80:4::227:103/128 Gigacom Systems PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS51341