SKH Network

Data as of 2026-09-27
BGP inherited
This organisation
Netblocks10
IPv6 9 prefixes (largest 2a13:a5c7:3309::/48)
Record ID246743421
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
2001:7f8:aa::237/128 SKH Network PEERINGDB ASSIGNED ● 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
217.106.184.64/26 SKH-GSSDC65 RIPE ASSIGNED PA ● low
2a13:a5c7:3309::/48 SKH-SYD RIPE ASSIGNED ● low
2a13:a5c7:3312::/48 skh-jp-e RIPE ASSIGNED ● low

IPv6 ranges (9)

Footprint over time

14 weekly snapshots · JSON
10 -9 netblocks since 2026-07-05
2026-07-05 peak 19 2026-09-27

Network trust

what's this?
RPKI hygiene: C how networks compare →
50.0% of checked blocks have valid RPKI ROA coverage (5 of 10)
Possible discrepancies (2)

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:3309::/48 /48 authorized for AS212985 — Mingjie Wu
2a13:a5c7:3312::/48 /48 authorized for AS212985 — Mingjie Wu

NIC Handles

AS212985 AS8342-MNT DUMY-RIPE DUMY-RIPE WMJ-MNT