NL-SAVVII-20250618
BGP inherited
Limited data: only 3 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 3 · 510 IPv4 addresses |
| Cluster ID | 210964831 |
| 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 | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 86.109.20.0/24 | NL-SAVVII-20250618 | RIPE | ASSIGNED PA | ● low |
| 194.107.180.0/24 | NL-SAVVII-20251016 | RIPE | ASSIGNED PA | ● low |
| 2a0d:7980:2::/48 | NL-SAVVII-20251201 | 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 NL-SAVVII-20250618 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.
| 2a0d:7980:2::/48 /48 | authorized for AS202053 — UpCloud Ltd |
| 194.107.180.0/24 /24 | authorized for AS202053 — UpCloud Ltd |
NIC Handles
DUMY-RIPE
DUMY-RIPE
lir-nl-savvii-1-MNT