VNODE-NL
Unresolved
Cluster stats
| Netblocks | 3 |
| All fragments | 4 blocks across 2 clusters |
| Cluster ID | 193022964 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a0f:9201:1::/56 | vNode-NL | RIPE | ASSIGNED | ● high |
| 45.150.43.0/28 | VNODE-NL | RIPE | ASSIGNED PA | ● low |
| 2a0f:9207::/48 | VNODE-NL | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
Possible discrepancies (2)
These blocks are registered to VNODE-NL 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.
| 2a0f:9207::/48 /48 | authorized for AS45009 — Rogier Krieger |
| 2a0f:9201:1::/56 /56 | authorized for AS45009 — Rogier Krieger |
NIC Handles
DUMY-RIPE
DUMY-RIPE
MNT-VNODE
VNDA24-RIPE