SMITH-NEPHEW
Cluster stats
Netblocks7
All fragments 11 blocks across 4 clusters
Cluster ID191895513
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 10 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-06

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
58.32.230.156/30 SMITH-NEPHEW-CO APNIC ASSIGNED NON-PORTABLE ● high
80.252.212.128/29 Smith_Nephew RIPE ASSIGNED PA ● low
194.128.168.240/28 SMITH-NEPHEW RIPE ASSIGNED PA ● low
194.200.45.0/24 SMITH-NEPHEW RIPE ASSIGNED PA ● low
212.42.12.48/28 SMITH-NEPHEW RIPE ASSIGNED PA ● low
213.58.208.80/29 SMITH-NEPHEW RIPE ASSIGNED PA ● low
2a00:2381:eb44::/48 SMITH-NEPHEW RIPE AGGREGATED-BY-LIR ● low

Network trust

what's this?
RPKI hygiene: C how networks compare →
57.1% of checked blocks have valid RPKI ROA coverage (4 of 7)
Possible discrepancies (1)

These blocks are registered to SMITH-NEPHEW 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:eb44::/48 /48 authorized for AS2856 — British Telecommunications PLC

NIC Handles

ALICE-MNT AS1849-MNT AS9186-MNT BTNET-MNT BearCom-MNT DUMY-RIPE DUMY-RIPE MAINT-CHINANET-SH MQ123-AP MQ123-AP