LSH

BGP inherited
Cluster stats
Netblocks10 · 326 IPv4 addresses
Registered in FO (7) · China (1) · Germany (1) · KZ (1)
All fragments 17 blocks across 6 clusters
Cluster ID208862936
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 8 shared RIR contact/maintainer handles
Registry names 5 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
218.30.0.0/24 LSH APNIC ASSIGNED NON-PORTABLE ● high
83.246.103.8/29 LSH-NET RIPE ASSIGNED PA ● low
87.247.8.36/30 LSH_International RIPE ASSIGNED PA ● low
212.55.52.204/30 LSH RIPE ASSIGNED PA ● low
212.55.52.208/30 LSH RIPE ASSIGNED PA ● low
212.55.53.8/29 LSH RIPE ASSIGNED PA ● low
212.55.53.16/29 LSH RIPE ASSIGNED PA ● low
212.55.53.24/29 lsh RIPE ASSIGNED PA ● low
212.55.60.160/30 LSH RIPE ASSIGNED PA ● low
212.55.60.224/27 LSH RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “LSH” — 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.

Network trust

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

These blocks are registered to LSH 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.

218.30.0.0/24 /24 authorized for AS4134 — No.31,Jin-rong Street

NIC Handles

DUMY-RIPE DUMY-RIPE FT-NET-MNT LS491-AP LS491-AP MAINT-CHINANET-GD SATELCOM-MNT SSERV-NET