Lunet AB
Cluster stats
Netblocks11
All fragments 24 blocks across 3 clusters
Cluster ID192094515
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 9 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
11 0 netblocks since 2026-07-05
2026-07-05 peak 11 2026-07-06

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
202.77.88.8/32 Lunet PEERINGDB ASSIGNED ● high
202.77.90.11/32 Lunet PEERINGDB ASSIGNED ● high
218.100.52.44/32 Lunet PEERINGDB ASSIGNED ● high
2001:7fa:11:4:0:a99:0:1/128 Lunet PEERINGDB ASSIGNED ● high
2001:df0:680:5::8/128 Lunet PEERINGDB ASSIGNED ● high
2001:df0:680:6::b/128 Lunet PEERINGDB ASSIGNED ● high
77.95.104.0/21 Lunet AB RIPE ALLOCATED PA ● low
185.230.24.0/22 Lunet AB RIPE ALLOCATED PA ● low
193.201.156.128/25 Lunet AB RIPE ASSIGNED PI ● low
209.206.16.0/24 LUNET RIPE SUB-ALLOCATED PA ● low
2a00:cc8::/32 Lunet AB RIPE ALLOCATED-BY-RIR ● low

Network trust

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

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

209.206.16.0/24 /24 authorized for AS13150 — CATO NETWORKS LTD

NIC Handles

AS2713 DUMY-RIPE DUMY-RIPE LUNET-NOC MAINT-AS13150 ORG-LEBA1-RIPE RIPE-NCC-END-MNT RIPE-NCC-HM-MNT il-catonetworks-1-mnt