Lyse Tele AS

NO-LYSE-ATEAAS
BGP inherited
Cluster stats
Netblocks6
All fragments 1,547 blocks across 1,222 clusters
Cluster ID210047670
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
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
79.160.80.208/29 NO-LYSE-ATEAAS RIPE ASSIGNED PA ● low
79.161.5.16/28 NO-LYSE-ATEAAS RIPE ASSIGNED PA ● low
81.167.253.80/29 NO-LYSE-ATEAAS RIPE ASSIGNED PA ● low
92.220.46.24/29 NO-LYSE-ATEAAS RIPE ASSIGNED PA ● low
109.247.92.224/29 NO-LYSE-ATEAAS RIPE ASSIGNED PA ● low
109.247.111.0/26 NO-LYSE-ATEAAS 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 (6 of 6)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE LYSE-MNT