PARKER-HANNIFIN-PLEIDELSHEIM-NET

BGP inherited
Cluster stats
Netblocks4
All fragments 98 blocks across 30 clusters
Cluster ID209963960
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

IP Ranges (4)

⬇ export CSV
CIDR Org name Registry Status Confidence
91.25.96.56/29 PARKER-HANNIFIN-PLEIDELSHEIM-NET RIPE ASSIGNED PA ● low
195.243.62.136/29 PARKER-HANNIFIN-PLEIDELSHEIM-NET RIPE ASSIGNED PA ● low
2003:c9:701f::/48 PARKER-HANNIFIN-PLEIDELSHEIM-NET RIPE ASSIGNED ● low
2003:de:e031::/48 PARKER-HANNIFIN-PLEIDELSHEIM-NET RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “PARKER HANNIFIN” — 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 30 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 (4 of 4)
No discrepancies found among checked blocks.

NIC Handles

DTAG-NIC DUMY-RIPE DUMY-RIPE