Husky Technologies
Cluster stats
| Netblocks | 20 |
| All fragments | 25 blocks across 3 clusters |
| Cluster ID | 191702461 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 14 shared RIR contact/maintainer handles |
| Registry names | 6 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (20)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 58.185.159.0/28 | HUSKY-SG | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 142.46.50.0/24 | Husky Technologies | BGP | ANNOUNCED | ● high |
| 192.75.80.0/24 | Husky Technologies | BGP | ANNOUNCED | ● high |
| 203.126.186.112/28 | HUSKY-SG | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 89.175.179.168/29 | Husky_CYS | RIPE | ASSIGNED PA | ● low |
| 146.0.147.136/29 | HUSKY-LU | RIPE | ASSIGNED PA | ● low |
| 146.0.149.8/29 | HUSKY-LU | RIPE | ASSIGNED PA | ● low |
| 146.0.149.176/29 | HUSKY-LU | RIPE | ASSIGNED PA | ● low |
| 193.86.24.232/30 | HUSKY-CZ | RIPE | ASSIGNED PA | ● low |
| 194.154.192.184/29 | HUSKY-LU | RIPE | ASSIGNED PA | ● low |
| 194.154.202.64/28 | HUSKY-LU | RIPE | ASSIGNED PA | ● low |
| 194.154.218.224/27 | HUSKY-LU | RIPE | ASSIGNED PA | ● low |
| 195.39.53.164/30 | HUSKY-CZ | RIPE | ASSIGNED PA | ● low |
| 195.46.254.240/28 | HUSKY-LU | RIPE | ASSIGNED PA | ● low |
| 210.245.163.88/30 | HUSKY-OIL-HK | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 2001:7e8:82dd::/56 | HUSKY-LU | RIPE | ALLOCATED-BY-LIR | ● low |
| 2001:7e8:82dd:100::/56 | HUSKY-LU | RIPE | ASSIGNED | ● low |
| 2001:7e8:8600:500::/56 | HUSKY-LU | RIPE | ASSIGNED | ● low |
| 2001:7e8:8600:b100::/56 | HUSKY-LU | RIPE | ASSIGNED | ● low |
| 2001:7e8:8600:c900::/56 | HUSKY-LU | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
90.0%
of checked blocks have valid RPKI ROA coverage
(18 of 20)
Possible discrepancies (5)
These blocks are registered to Husky Technologies 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.
| 2001:7e8:82dd::/56 /56 | authorized for AS6661 — POST Luxembourg |
| 2001:7e8:82dd:100::/56 /56 | authorized for AS6661 — POST Luxembourg |
| 2001:7e8:8600:500::/56 /56 | authorized for AS6661 — POST Luxembourg |
| 2001:7e8:8600:b100::/56 /56 | authorized for AS6661 — POST Luxembourg |
| 2001:7e8:8600:c900::/56 /56 | authorized for AS6661 — POST Luxembourg |
NIC Handles
AH1343-AP
AS32201
AS6661-MNT
BL642-AP
DUMY-RIPE
DUMY-RIPE
GTSCZ-MNT
KA18-AP
MAINT-HK-HKBNESL
MAINT-SG-SINGNET
MH1716-AP
MTU-NOC
+2 more