PL-Server_Management_LL

BGP inherited
Cluster stats
Netblocks6
All fragments 13 blocks across 2 clusters
Cluster ID204962468
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-13

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.133.8.248/30 PL-Server_Management_LL RIPE ASSIGNED PA ● low
5.133.9.78/32 PL-Server_Management_LL RIPE ASSIGNED PA ● low
5.133.9.79/32 PL-Server_Management_LL RIPE ASSIGNED PA ● low
5.133.11.90/32 PL-Server_Management_LL RIPE ASSIGNED PA ● low
37.28.152.53/32 PL-Server_Management_LL RIPE ASSIGNED PA ● low
178.255.44.44/30 PL-Server_Management_LL RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-ARTNET-API