Lyse Tele AS

NO-LYSE-JOTUNAS
BGP inherited
Cluster stats
Netblocks8
All fragments 1,547 blocks across 1,222 clusters
Cluster ID204872701
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-13

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
79.160.177.48/29 NO-LYSE-JOTUNAS RIPE ASSIGNED PA ● low
79.160.226.136/29 NO-LYSE-JOTUNAS RIPE ASSIGNED PA ● low
81.167.50.104/29 NO-LYSE-JOTUNAS RIPE ASSIGNED PA ● low
81.167.50.120/29 NO-LYSE-JOTUNAS RIPE ASSIGNED PA ● low
81.167.55.0/24 NO-LYSE-JOTUNAS RIPE ASSIGNED PA ● low
92.220.126.176/29 NO-LYSE-JOTUNAS RIPE ASSIGNED PA ● low
92.221.249.128/28 NO-LYSE-JOTUNAS RIPE ASSIGNED PA ● low
109.247.50.152/29 NO-LYSE-JOTUNAS RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “NO LYSE” — 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.
Combined view of all 1,222 name-family clusters →
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 (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE LYSE-MNT