NL-SPLIETHOFF
BGP inherited
Cluster stats
| Netblocks | 6 |
| All fragments | 9 blocks across 2 clusters |
| Cluster ID | 205835893 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
4 weekly snapshots · JSON
6
0 netblocks since 2026-07-05
2026-07-05
peak 6
2026-07-19
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.88.57.0/25 | NL-SPLIETHOFF | RIPE | ASSIGNED PA | ● low |
| 45.88.57.128/28 | NL-SPLIETHOFF | RIPE | ASSIGNED PA | ● low |
| 45.88.57.144/29 | NL-SPLIETHOFF | RIPE | ASSIGNED PA | ● low |
| 2a0d:3480:a::/48 | NL-SPLIETHOFF | RIPE | ASSIGNED | ● low |
| 2a0d:3480:b::/48 | NL-SPLIETHOFF | RIPE | ASSIGNED | ● low |
| 2a0d:3480:c::/48 | NL-SPLIETHOFF | RIPE | ASSIGNED | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “NL SPLIETHOFF” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- NL-SPLIETHOFF-CORE 3 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- SPLIETHOFF sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(6 of 6)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
MNT-FUSIONYX
SPLIETHOFF-MNT