NL-RIJNDATA
BGP inherited
Cluster stats
| Netblocks | 2 |
| All fragments | 4 blocks across 2 clusters |
| Cluster ID | 209890175 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 46.21.169.128/28 | NL-RIJNDATA | RIPE | ASSIGNED PA | ● low |
| 2a02:27f8:1007::/48 | NL-RIJNDATA | RIPE | ALLOCATED-BY-LIR | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
Possible discrepancies (1)
These blocks are registered to NL-RIJNDATA 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.
| 2a02:27f8:1007::/48 /48 | authorized for AS42755 — DataFiber Group B.V. |
NIC Handles
DUMY-RIPE
DUMY-RIPE
MNT-RIJNDATABV