PP Lurenet
PP "Lurenet"
Cluster stats
Netblocks7
All fragments 458 blocks across 116 clusters
Cluster ID191657046
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 10 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.53.116.0/24 PP "Lurenet" BGP ANNOUNCED ● high
194.50.167.0/24 PP "Lurenet" BGP ANNOUNCED ● high
194.145.227.0/24 PP "Lurenet" BGP ANNOUNCED ● high
195.39.240.0/24 PP "Lurenet" BGP ANNOUNCED ● high
195.191.200.0/24 PP "Lurenet" BGP ANNOUNCED ● high
195.191.201.0/24 PP "Lurenet" BGP ANNOUNCED ● high
2001:678:b4c::/48 PP "Lurenet" RIPE ASSIGNED PI ● high

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
Possible discrepancies (1)

These blocks are registered to PP "Lurenet" 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.

2001:678:b4c::/48 /48 authorized for AS50643 — Maslianikov Mykola

NIC Handles

AS59956 DL-MNT DUMY-RIPE DUMY-RIPE LURENET-MNT LURENET-MNT MASLIANIKOV-MNT MASLIANIKOV-MNT ORG-PA372-RIPE RIPE-NCC-END-MNT