JNET TELECOM
JNET
Cluster stats
| Netblocks | 8 |
| All fragments | 27 blocks across 3 clusters |
| Cluster ID | 193183520 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 14 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
8
0 netblocks since 2026-07-05
2026-07-05
peak 8
2026-07-06
IP Ranges (8)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 14.136.197.128/26 | JNET | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 61.244.116.128/26 | JNET | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 88.204.156.0/29 | JNET | RIPE | ASSIGNED PA | ● low |
| 95.56.227.176/28 | JNET | RIPE | ASSIGNED PA | ● low |
| 95.56.240.160/27 | JNET | RIPE | ASSIGNED PA | ● low |
| 125.215.221.64/26 | JNET | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 144.79.20.0/24 | JNET | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 144.79.21.0/24 | JNET | APNIC | ALLOCATED NON-PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
87.5%
of checked blocks have valid RPKI ROA coverage
(7 of 8)
Possible discrepancies (2)
These blocks are registered to JNET TELECOM 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.
| 144.79.20.0/24 /24 | authorized for AS154386 — Javed Net |
| 144.79.21.0/24 /24 | authorized for AS154386 — Javed Net |
NIC Handles
AC2009-AP
AJ671-AP
BNA2-AP
CH134-AP
CH134-AP
DUMY-RIPE
DUMY-RIPE
JNFA1-AP
JNFA1-AP
KNIC-MNT
MAINT-HK-CTI
MAINT-HK-PCCW-BIA-CS
+2 more