IPv4_Range_for_Husqvarna_over_NetCom_BW
BGP inherited
Cluster stats
| Netblocks | 9 |
| All fragments | 518 blocks across 387 clusters |
| Cluster ID | 205752846 |
| 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 | |
Footprint over time
4 weekly snapshots · JSON
9
0 netblocks since 2026-07-05
2026-07-05
peak 9
2026-07-13
IP Ranges (9)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 217.78.170.32/29 | IPv4_Range_for_Husqvarna_AB_over_NetCom_BW | RIPE | ASSIGNED PA | ● low |
| 217.78.171.16/29 | IPv4_Range_for_Husqvarna_over_NetCom_BW | RIPE | ASSIGNED PA | ● low |
| 217.78.171.24/29 | IPv4_Range_for_Husqvarna_over_NetCom_BW | RIPE | ASSIGNED PA | ● low |
| 217.78.171.32/29 | IPv4_Range_for_Husqvarna_over_NetCom_BW | RIPE | ASSIGNED PA | ● low |
| 217.78.171.40/29 | IPv4_Range_for_Husqvarna_over_NetCom_BW | RIPE | ASSIGNED PA | ● low |
| 217.78.171.96/28 | IPv4_Range_for_Husqvarna_over_NetCom_BW | RIPE | ASSIGNED PA | ● low |
| 217.78.171.112/29 | IPv4_Range_for_Husqvarna_over_NetCom_BW | RIPE | ASSIGNED PA | ● low |
| 217.78.171.120/29 | IPv4_Range_for_Husqvarna_over_NetCom_BW | RIPE | ASSIGNED PA | ● low |
| 217.78.173.40/29 | IPv4_Range_for_Husqvarna_AB_over_NetCom_BW | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “IPv4 Range for” — 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.
- IPv4_Range_for_e-business_over_NetCom_BW 15 blocks
- IPv4_Range_for_Stadtverwaltung_Aalen_over_NetCom_BW 14 blocks
- IPv4_Range_for_Carl_Zeiss_AG_over_NetCom_BW 8 blocks
- IPv4_Range_for_Diakonie_Stetten_over_NetCom_BW 6 blocks
- IPv4_Range_for_Lindau_Tourismus_und_Kongress_over_NetCom_BW 5 blocks
- IPv4_Range_for_Schwarz_IT_over_NetCom_BW 5 blocks
- IPv4_Range_for_Netze_BW_NETZ_KDIN_over_NetCom_BW 4 blocks
- IPv4_Range_for_Stadt_Muehlacker_over_NetCom_BW 4 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.
- IPv4_Range_for_Concept_und_Service_over_NetCom_BW via NetCom BW GmbH sub-allocation
- BRSL-IPV4-AMWEB-RANGE3-20120703 via EKCO CLOUD IRELAND LIMITED sub-allocation
- IPv4_Range_for_GABO_STAHL_over_NetCom_BW via NetCom BW GmbH sub-allocation
- IPv4_RANGE_Telenot_Electronic_GmbH_over_NETCOM_BW via NetCom BW GmbH sub-allocation
- IPv4_Range_for_Doederlein_Spedition_over_NetCom_BW via NetCom BW GmbH sub-allocation
- AWV-TELEMATICA-IPV4-RANGE-INTERNETKLANTEN sub-allocation
- AWV-TELEMATICA-IPV4-RANGE-EIGEN-NETWERK sub-allocation
- IPv4_Range_STADTVERWALTUNG_AALEN_over_NETCOM_BW via NetCom BW GmbH sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(9 of 9)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
ODR-TKG-MNT