Robert van der Meulen
BGP inherited
Cluster stats
Netblocks6
All fragments 8 blocks across 2 clusters
Cluster ID191802773
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 8 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
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-06

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
2001:7f8:d0::ded8:1/128 Robert van der Meulen PEERINGDB ASSIGNED ● high
2001:7f8:10f::ded8:1629/128 Robert van der Meulen PEERINGDB ASSIGNED ● high
2602:fed2:fff:ffff:6::f8/128 Robert van der Meulen PEERINGDB ASSIGNED ● high
2a0e:f7c0::/29 Robert van der Meulen BGP ANNOUNCED ● high
45.145.144.0/22 Robert van der Meulen RIPE ALLOCATED PA ● low
2a0e:f7c0::/29 Robert van der Meulen RIPE ALLOCATED-BY-RIR ● low

Network trust

what's this?
RPKI hygiene: C how networks compare →
66.7% of checked blocks have valid RPKI ROA coverage (4 of 6)
Possible discrepancies (1)

These blocks are registered to Robert van der Meulen 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.

45.145.144.0/22 /22 authorized for AS393894 — MSR PRIVATE CABLE TV

NIC Handles

AS57048 AS57048 DUMY-RIPE DUMY-RIPE ORG-RVDM2-RIPE RIPE-NCC-HM-MNT rvdm rvdm