LYSGLIMT

BGP inherited
Cluster stats
Netblocks6 · 2,042 IPv4 addresses
All fragments 9 blocks across 4 clusters
Cluster ID205246057
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name 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
94.143.65.0/24 LYSGLIMT RIPE ASSIGNED PA ● high
94.143.66.0/23 LYSGLIMT RIPE ASSIGNED PA ● high
94.143.68.0/22 LYSGLIMT RIPE ASSIGNED PA ● high
94.143.64.0/25 LYSGLIMT RIPE ASSIGNED PA ● low
94.143.64.128/26 LYSGLIMT RIPE ASSIGNED PA ● low
94.143.64.192/26 LYSGLIMT RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

Arild-Avd-leder DUMY-RIPE DUMY-RIPE MNT-ROGERLARSEN