van-den-heuvel
BGP inherited
Cluster stats
| Netblocks | 2 |
| All fragments | 5 blocks across 3 clusters |
| Cluster ID | 209302066 |
| 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 | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 62.177.237.64/28 | Van-den-Heuvel | RIPE | ASSIGNED PA | ● low |
| 62.177.255.32/29 | van-den-heuvel | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “van den heuvel” — 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.
- VAN_DEN_HEUVEL_MAKELAARS 2 blocks
- van den Heuvel Bjorn 1 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.
- Nijenburgh Beheer Hettenheuvelweg sub-allocation
- Heuvelmangroep via Odido Netherlands B.V. sub-allocation
- MTSVDHEUVEL-BAKEL via Signet B.V. sub-allocation
- gerechtsdeurwaarders_vd_heuvel via Odido Netherlands B.V. sub-allocation
- gerechtsdeurwaarders_vd_heuvel_access_line1 via Odido Netherlands B.V. sub-allocation
- gerechtsdeurwaarders_vd_heuvel_access_line2 via Odido Netherlands B.V. sub-allocation
- GGZ_HEUVELRUG_BV via Vodafone Libertel B.V. sub-allocation
- Moddeleur_27_5171_SL_Kaatsheuvel via Odido Netherlands B.V. sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
NL-BBNET-MNT