Comms FM

Commsfm
Registry
Cluster stats
Netblocks7
All fragments 8 blocks across 2 clusters
Cluster ID209254296
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
81.137.3.144/29 CommsFM RIPE ASSIGNED PA ● low
81.138.241.0/29 Commsfm RIPE ASSIGNED PA ● low
81.142.151.8/29 CommsFM RIPE ASSIGNED PA ● low
217.37.130.152/29 commsfm RIPE ASSIGNED PA ● low
217.45.210.136/29 Commsfm RIPE ASSIGNED PA ● low
2a00:2381:1495::/48 COMMSFM RIPE AGGREGATED-BY-LIR ● low
2a00:2381:17bb::/48 COMMSFM RIPE AGGREGATED-BY-LIR ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
Possible discrepancies (2)

These blocks are registered to Commsfm but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2a00:2381:1495::/48 /48 authorized for AS2856 — British Telecommunications Limited
2a00:2381:17bb::/48 /48 authorized for AS2856 — British Telecommunications Limited

NIC Handles

BTNET-MNT DUMY-RIPE DUMY-RIPE