JNPOST

BGP inherited
Cluster stats
Netblocks7
All fragments 8 blocks across 2 clusters
Cluster ID210159416
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
60.208.73.64/29 JNPOST APNIC ASSIGNED NON-PORTABLE ● low
60.208.73.72/29 JNPOST APNIC ASSIGNED NON-PORTABLE ● low
60.216.4.184/29 JNPOST APNIC ASSIGNED NON-PORTABLE ● low
124.128.80.232/30 JNPOST APNIC ASSIGNED NON-PORTABLE ● low
124.128.159.208/29 JNPOST APNIC ASSIGNED NON-PORTABLE ● low
221.214.15.152/30 JNPOST APNIC ASSIGNED NON-PORTABLE ● low
221.214.15.156/30 JNPOST APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “JNPOST” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.
  • JNPOST3-GOV via CNCGROUP IP network of ShangHai IDC sub-allocation
  • JNPOST2-GOV via CNCGROUP IP network of ShangHai IDC sub-allocation
  • JNPOST-GOV via CNCGROUP IP network of ShangHai IDC sub-allocation
  • JNPOSTOFFICE-GOV via CNCGROUP IP network of ShangHai IDC sub-allocation

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
No discrepancies found among checked blocks.

NIC Handles

DS95-AP DS95-AP MAINT-CNCGROUP-SD