TONGKUN
BGP inherited
Cluster stats
| Netblocks | 6 · 290 IPv4 addresses |
| Cluster ID | 206440099 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 16 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
3 weekly snapshots · JSON
6
0 netblocks since 2026-07-05
2026-07-05
peak 6
2026-07-13
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 116.246.12.32/30 | TONGKUN | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 116.246.18.216/29 | TONGKUN | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 122.225.82.0/28 | TONGKUN-GROUP | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 122.225.82.16/29 | TONGKUN-GROUP | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 222.66.22.164/30 | TONGKUN | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 210.83.163.0/24 | tongkun-group | APNIC | ASSIGNED NON-PORTABLE | ● low |
Possibly related to this organisation
what's this?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.
- pinghu-tongkun-group sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(6 of 6)
Possible discrepancies (1)
These blocks are registered to TONGKUN 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.
| 210.83.163.0/24 /24 | authorized for AS9929 — CNCGROUP IP network of ShangHai IDC |
NIC Handles
AC1591-AP
AC1602-AP
CJ55-AP
MAINT-CHINANET-SH
MAINT-CN-CHINANET-ZJ-JX
MAINT-CN-ZM28
ML1725-AP
ML1725-AP
TC254-AP
TC254-AP
YX1409-AP
YX1410-AP
+4 more