NKN-LPSC-KL
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 2 |
| IPv6 | 1 prefix (largest 2405:8a00:a052::/48) |
| All fragments | 4 blocks across 3 clusters |
| Cluster ID | 213356639 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 14.139.174.16/28 | NKN-LPSC-KL | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 2405:8a00:a052::/48 | NKN-LPSC-KL | APNIC | ASSIGNED NON-PORTABLE | ● high |
IPv6 ranges (1)
| CIDR |
|---|
| 2405:8a00:a052::/48 |
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 (1)
These blocks are registered to NKN-LPSC-KL 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.
| 2405:8a00:a052::/48 /48 | authorized for AS55824 — National Knowledge Network |
NIC Handles
AN2607-AP
MAINT-RSMANI-NKN-IN
NNA22-AP
SKS121-AP