AMOLF-NET

BGP inherited
Cluster stats
Netblocks7 · 2,809 IPv4 addresses
All fragments 8 blocks across 2 clusters
Cluster ID208822741
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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
145.101.40.0/22 AMOLF RIPE LEGACY ● high
192.16.189.0/24 AMOLF RIPE LEGACY ● high
192.87.167.0/24 AMOLF-NET RIPE LEGACY ● low
194.171.68.0/24 AMOLF-NET RIPE ASSIGNED PA ● low
194.171.69.0/24 AMOLF-NET RIPE ASSIGNED PA ● low
194.171.70.0/24 AMOLF-NET RIPE ASSIGNED PA ● low
194.171.110.0/23 AMOLF-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “AMOLF NET” — 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: B how networks compare →
85.7% of checked blocks have valid RPKI ROA coverage (6 of 7)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE ORG-AA1137-RIPE SN-LIR-MNT SURF-AUTO-MNT