NANPING-TELECOM-NANPING-FJ
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 3 · 5,888 IPv4 addresses |
| All fragments | 9 blocks across 6 clusters |
| Cluster ID | 217136008 |
| Registry | APNIC |
| Customers | find 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 · report an issue | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 220.160.240.0/20 | NANPING-TELECOM-NANPING-FJ | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 222.78.192.0/22 | NANPING-TELECOM-NANPING-FJ | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 222.78.252.0 – 222.78.254.255 | NANPING-TELECOM-NANPING-FJ | APNIC | ASSIGNED NON-PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
RPKI-inferred operator
No.31,Jin-rong Street
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
CA67-AP
CA67-AP
MAINT-CHINANET-FJ