JK Network IPs
BGP inherited
Cluster stats
| Netblocks | 2 |
| All fragments | 14 blocks across 2 clusters |
| Cluster ID | 206172148 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a06:a005:210::/44 | JK Network IPs | RIPE | ASSIGNED | ● low |
| 2a0e:b107:1950::/44 | JK Network IPs | RIPE | ALLOCATED-BY-LIR | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
Possible discrepancies (2)
These blocks are registered to JK Network IPs 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.
| 2a0e:b107:1950::/44 /44 | authorized for AS207705 — Jyun-Kai Hu |
| 2a06:a005:210::/44 /44 | authorized for AS207705 — Jyun-Kai Hu |
NIC Handles
DUMY-RIPE
DUMY-RIPE
ORG-JK96-RIPE
ROUTE48-MNT
SBMT
WHOJK-MNT