SKH Network
Cluster stats
| Netblocks | 19 |
| All fragments | 37 blocks across 17 clusters |
| Cluster ID | 191710958 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 11 shared RIR contact/maintainer handles |
| Registry names | 13 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (19)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 203.198.162.192/29 | skh-chi-fai-hk | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 203.198.164.120/29 | skh-kei-lok-hk | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 203.198.170.104/29 | skh-wei-lun-sch | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 2406:840:1f:1000:0:21:2985:1/128 | SKH Network | PEERINGDB | ASSIGNED | ● high |
| 2602:f92a:1315::25/128 | SKH Network | PEERINGDB | ASSIGNED | ● high |
| 2602:f92a:1315:2::43/128 | SKH Network | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:10::19d/128 | SKH Network | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:13::10e/128 | SKH Network | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:16::10f/128 | SKH Network | PEERINGDB | ASSIGNED | ● high |
| 194.212.232.64/26 | SKH-CZ | RIPE | ASSIGNED PA | ● low |
| 217.106.184.64/26 | SKH-GSSDC65 | RIPE | ASSIGNED PA | ● low |
| 2a13:a5c7:3301::/48 | SKH-HK | RIPE | ASSIGNED | ● low |
| 2a13:a5c7:3302::/48 | SKH-JP | RIPE | ASSIGNED | ● low |
| 2a13:a5c7:3303::/48 | SKH-DE | RIPE | ASSIGNED | ● low |
| 2a13:a5c7:3304::/48 | SKH-GB | RIPE | ASSIGNED | ● low |
| 2a13:a5c7:3306::/48 | SKH-DE | RIPE | ASSIGNED | ● low |
| 2a13:a5c7:3307::/48 | SKH-AL | RIPE | ASSIGNED | ● low |
| 2a13:a5c7:3309::/48 | SKH-SYD | RIPE | ASSIGNED | ● low |
| 2a13:a5c7:3312::/48 | skh-jp-e | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
78.9%
of checked blocks have valid RPKI ROA coverage
(15 of 19)
Possible discrepancies (8)
These blocks are registered to SKH Network 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.
| 2a13:a5c7:3301::/48 /48 | authorized for AS212985 — Mingjie Wu |
| 2a13:a5c7:3302::/48 /48 | authorized for AS212985 — Mingjie Wu |
| 2a13:a5c7:3303::/48 /48 | authorized for AS212985 — Mingjie Wu |
| 2a13:a5c7:3307::/48 /48 | authorized for AS212985 — Mingjie Wu |
| 2a13:a5c7:3306::/48 /48 | authorized for AS212985 — Mingjie Wu |
| 2a13:a5c7:3304::/48 /48 | authorized for AS212985 — Mingjie Wu |
| 2a13:a5c7:3309::/48 /48 | authorized for AS212985 — Mingjie Wu |
| 2a13:a5c7:3312::/48 /48 | authorized for AS212985 — Mingjie Wu |
NIC Handles
AS212985
AS8342-MNT
CES-IP-MNT
DUMY-RIPE
DUMY-RIPE
LCW19-AP
LM1045-AP
MAINT-HK-IMS-CS
SMC10-AP
TA29-AP
WMJ-MNT