PERNOD_RICARD

BGP inherited
Cluster stats
Netblocks7
Registered in Spain (4) · France (2) · GH (1)
All fragments 23 blocks across 10 clusters
Cluster ID210350439
RegistryAFRINIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 7 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
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
109.26.131.96/29 PERNOD-RICARD RIPE ASSIGNED PA ● low
195.57.116.104/29 PERNOD_RICARD RIPE ASSIGNED PA ● low
195.57.126.128/29 PERNOD_RICARD RIPE ASSIGNED PA ● low
195.77.162.248/29 PERNOD_RICARD RIPE ASSIGNED PA ● low
195.77.203.240/29 PERNOD_RICARD RIPE ASSIGNED PA ● low
197.159.133.16/30 PERNOD-RICARD AFRINIC ASSIGNED PA ● low
213.223.163.144/28 PERNOD-RICARD RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

COMSYS-MNT DUMY-RIPE DUMY-RIPE LDCOM-PRO-MNT MAINT-AS3352 SyS26 SyS26