COMA

BGP inherited
Cluster stats
Netblocks6 · 274 IPv4 addresses
Registered in Czechia (3) · Australia (2) · Germany (1)
All fragments 13 blocks across 5 clusters
Cluster ID209880822
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 8 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
59.154.85.232/30 COMA APNIC ASSIGNED NON-PORTABLE ● low
61.88.116.128/30 COMA APNIC ASSIGNED NON-PORTABLE ● low
62.245.168.40/29 COMA-NET RIPE ASSIGNED PA ● low
82.100.29.0/25 COMA RIPE ASSIGNED PA ● low
82.100.29.128/25 COMA RIPE ASSIGNED PA ● low
217.169.181.168/29 COMA RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “COMA” — 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: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)
No discrepancies found among checked blocks.

NIC Handles

DIALTELECOM-MNT DUMY-RIPE DUMY-RIPE MAINT-OPTUSCOM-AP MNET-MNT OA3-AP OA3-AP UNIENTCZ-MNT