XN-TELECOM
Cluster stats
| Netblocks | 17 |
| All fragments | 21 blocks across 4 clusters |
| Cluster ID | 193120994 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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
2 weekly snapshots · JSON
17
0 netblocks since 2026-07-05
2026-07-05
peak 17
2026-07-06
IP Ranges (17)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 202.100.131.0 – 202.100.131.87 | XN-TELECOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.100.131.128 – 202.100.131.151 | XN-TELECOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.100.132.0/28 | XN-TELECOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.100.132.128/25 | XN-TELECOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.100.144.0 – 202.100.158.255 | XN-TELECOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.100.159.0/30 | XN-TELECOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.100.159.48/28 | XN-TELECOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 218.95.228.0/27 | XN-TELECOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 218.95.228.32/29 | XN-TELECOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 218.95.228.40/30 | XN-TELECOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 218.95.228.64/27 | XN-TELECOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 218.95.228.120/30 | XN-TELECOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 218.95.228.124/30 | XN-TELECOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 218.95.228.136/30 | XN-TELECOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 218.95.228.144/28 | XN-TELECOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 218.95.240.0/25 | XN-TELECOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 218.95.241.0/24 | XN-TELECOM | 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
(17 of 17)
No discrepancies found among checked blocks.
NIC Handles
HJ537-AP
MAINT-CHINANET-QH
XP13-AP