Lucas van Beek
Cluster stats
Netblocks9
All fragments 205 blocks across 48 clusters
Cluster ID191556033
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 10 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-06

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.249.208.56/32 Lucas van Beek PEERINGDB ASSIGNED ● high
2001:7f8:1:0:a500:21:5577:1/128 Lucas van Beek PEERINGDB ASSIGNED ● high
2001:7f8:10f::3:4a19:254/128 Lucas van Beek PEERINGDB ASSIGNED ● high
2a07:54c7:5f00::/40 Lucas van Beek RIPE ASSIGNED ● high
2a07:54c7:5f00::/44 Lucas van Beek BGP ANNOUNCED ● high
2a07:54c7:5f10::/48 Lucas van Beek BGP ANNOUNCED ● high
2a07:54c7:5ffe::/48 Lucas van Beek BGP ANNOUNCED ● high
2a07:e345:200::/48 Lucas van Beek BGP ANNOUNCED ● high
2a07:e345:200::/48 Lucas van Beek RIPE ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (9 of 9)
Possible discrepancies (1)

These blocks are registered to Lucas van Beek but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2a07:54c7:5f00::/40 /40 authorized for AS216455 — Sting Alleman

NIC Handles

AS215577 AS215577 DUMY-RIPE DUMY-RIPE LUCAS-MNT LUCAS-MNT ORG-LVB3-RIPE STING-MNT XYPHEN-MNT XYPHEN-MNT