BOLLIGER S.P.A.

bolliger
GLEIF verified
LEI
815600A1261B25838D36
Registered name
BOLLIGER S.P.A.
Jurisdiction
Ultimate parent
No parent on file in GLEIF
Cluster stats
Netblocks7
All fragments 8 blocks across 2 clusters
Cluster ID209527956
RegistryPEERINGDB
Owner jurisdictionIT
Customersfind customers using this network →
Evidence & provenance ?
Attribution GLEIF legal-entity match
Legal identityLEI 815600A1261B25838D36
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 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
185.1.105.9/32 bolliger PEERINGDB ASSIGNED ● high
185.1.105.24/32 bolliger PEERINGDB ASSIGNED ● high
2001:7f8:bf:1::9/128 bolliger PEERINGDB ASSIGNED ● high
2001:7f8:bf:1::18/128 bolliger PEERINGDB ASSIGNED ● high
213.221.203.240/29 BOLLIGER-NET RIPE ASSIGNED PA ● low
213.221.227.152/29 BOLLIGER-NET RIPE ASSIGNED PA ● low
217.192.62.40/29 BOLLIGER-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

AS59808 CH-LAN-MNT CH-UNISOURCE-MNT DUMY-RIPE DUMY-RIPE