PALRAM

BGP inherited
Cluster stats
Netblocks10
All fragments 15 blocks across 4 clusters
Cluster ID209109780
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.219.65.184/29 PALRAM-LTD RIPE ASSIGNED PA ● low
80.179.185.96/28 PALRAM RIPE ASSIGNED PA ● low
82.80.88.152/29 PALRAM-LTD RIPE ASSIGNED PA ● low
82.80.93.152/29 PALRAM RIPE ASSIGNED PA ● low
82.80.101.40/29 PALRAM RIPE ASSIGNED PA ● low
192.117.0.224/28 PALRAM RIPE ASSIGNED PA ● low
212.179.165.96/27 PALRAM RIPE ASSIGNED PA ● low
212.179.180.0/26 PALRAM RIPE ASSIGNED PA ● low
212.199.123.200/29 PALRAM RIPE ASSIGNED PA ● low
212.199.157.160/27 Palram-Ltd RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (10 of 10)
No discrepancies found among checked blocks.

NIC Handles

AS8551-MNT AS9116-MNT DUMY-RIPE DUMY-RIPE