DSV Panalpina

BGP inherited
Cluster stats
Netblocks9
Registered in South Africa (2) · Hong Kong (1) · Netherlands (1) · United States (1)
All fragments 10 blocks across 2 clusters
Cluster ID213183669
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.247.139.82/32 DSV Panalpina PEERINGDB ASSIGNED ● high
193.239.118.96/32 DSV Panalpina PEERINGDB ASSIGNED ● high
196.60.9.49/32 DSV Panalpina PEERINGDB ASSIGNED ● high
196.60.9.50/32 DSV Panalpina PEERINGDB ASSIGNED ● high
206.53.174.18/32 DSV Panalpina PEERINGDB ASSIGNED ● high
2001:7f8:13::a504:9362:1/128 DSV Panalpina PEERINGDB ASSIGNED ● high
2001:43f8:6d0::9:49/128 DSV Panalpina PEERINGDB ASSIGNED ● high
2001:43f8:6d0::9:50/128 DSV Panalpina PEERINGDB ASSIGNED ● high
2606:a980:0:7::12/128 DSV Panalpina PEERINGDB ASSIGNED ● high

Possibly related to this organisation

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

NIC Handles

AS49362