COME-NET

BGP inherited
Cluster stats
Netblocks6
Registered in Germany (3) · Italy (3)
All fragments 12 blocks across 6 clusters
Cluster ID209414558
RegistryRIPE
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

Footprint over time

3 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-12

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
2.119.192.100/30 COME RIPE ASSIGNED PA ● low
145.253.193.192/29 COME-NET RIPE ASSIGNED PA ● low
151.189.191.216/29 COME-NET RIPE ASSIGNED PA ● low
213.23.84.0/27 COME-NET RIPE ASSIGNED PA ● low
217.56.115.60/30 COME RIPE ASSIGNED PA ● low
217.220.229.181/32 COME RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “COME” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

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

NIC Handles

ALBACOM-MNT ARCOR-MNT DUMY-RIPE DUMY-RIPE INTERB-MNT