LAKESMERE

BGP inherited
Cluster stats
Netblocks9
Cluster ID208893597
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

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

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
81.3.68.176/30 LAKESMERE RIPE ASSIGNED PA ● low
81.3.68.192/27 LAKESMERE RIPE ASSIGNED PA ● low
193.195.238.188/30 LAKESMERE RIPE ASSIGNED PA ● low
212.87.74.32/29 LAKESMERE RIPE ASSIGNED PA ● low
212.87.78.12/30 LAKESMERE RIPE ASSIGNED PA ● low
212.87.78.32/27 LAKESMERE RIPE ASSIGNED PA ● low
212.240.12.8/30 LAKESMERE RIPE ASSIGNED PA ● low
212.240.95.96/28 LAKESMERE RIPE ASSIGNED PA ● low
2a00:2381:876::/48 LAKESMERE-LTD RIPE AGGREGATED-BY-LIR ● low

Network trust

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

These blocks are registered to LAKESMERE 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:876::/48 /48 authorized for AS2856 — British Telecommunications Limited

NIC Handles

BTNET-MNT DUMY-RIPE DUMY-RIPE NEWNET-MNT VODAFONE-WORLDWIDE-MNTNER