Sandro Bolliger

BGP inherited
Cluster stats
Netblocks8
All fragments 44 blocks across 2 clusters
Cluster ID213183906
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
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
91.206.52.68/32 Sandro Bolliger PEERINGDB ASSIGNED ● high
185.1.59.155/32 Sandro Bolliger PEERINGDB ASSIGNED ● high
185.1.105.4/32 Sandro Bolliger PEERINGDB ASSIGNED ● high
185.1.205.6/32 Sandro Bolliger PEERINGDB ASSIGNED ● high
2001:7f8:24::44/128 Sandro Bolliger PEERINGDB ASSIGNED ● high
2001:7f8:bf:1::4/128 Sandro Bolliger PEERINGDB ASSIGNED ● high
2001:7f8:cc:333::155/128 Sandro Bolliger PEERINGDB ASSIGNED ● high
2001:7f8:111:42::3013:1/128 Sandro Bolliger PEERINGDB ASSIGNED ● high

Possibly related to this organisation

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

NIC Handles

AS12307