Alcom

BGP inherited
Cluster stats
Netblocks12
All fragments 49 blocks across 27 clusters
Cluster ID204695493
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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 (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
193.110.224.144/32 Alcom PEERINGDB ASSIGNED ● high
194.68.123.135/32 Alcom PEERINGDB ASSIGNED ● high
194.68.128.135/32 Alcom PEERINGDB ASSIGNED ● high
195.69.119.135/32 Alcom PEERINGDB ASSIGNED ● high
195.245.240.135/32 Alcom PEERINGDB ASSIGNED ● high
2001:7f8:7:b::3238:1/128 Alcom PEERINGDB ASSIGNED ● high
2001:7f8:d:fb::135/128 Alcom PEERINGDB ASSIGNED ● high
2001:7f8:d:fc::135/128 Alcom PEERINGDB ASSIGNED ● high
2001:7f8:d:fe::135/128 Alcom PEERINGDB ASSIGNED ● high
2001:7f8:d:ff::135/128 Alcom PEERINGDB ASSIGNED ● high
195.109.105.104/29 ALCOM RIPE ASSIGNED PA ● low
212.123.30.240/28 ALCOM RIPE ASSIGNED PA ● low

Network trust

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

NIC Handles

AS3238 DUMY-RIPE DUMY-RIPE NLNET-MNT TELENET-OPS-MNT