XN-TELCOM

Data as of 2026-09-20
BGP inherited
This organisation
Netblocks9
Record ID241180823
RegistryAPNIC
Customerssee who runs inside 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 (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
202.100.128.0/27 XN-TELCOM APNIC ASSIGNED NON-PORTABLE ● low
202.100.128.32/27 XN-TELCOM APNIC ASSIGNED NON-PORTABLE ● low
202.100.128.64/28 XN-TELCOM APNIC ASSIGNED NON-PORTABLE ● low
202.100.128.80/28 XN-TELCOM APNIC ASSIGNED NON-PORTABLE ● low
202.100.128.96/27 XN-TELCOM APNIC ASSIGNED NON-PORTABLE ● low
202.100.128.128/27 XN-TELCOM APNIC ASSIGNED NON-PORTABLE ● low
202.100.128.160/28 XN-TELCOM APNIC ASSIGNED NON-PORTABLE ● low
202.100.128.192/27 XN-TELCOM APNIC ASSIGNED NON-PORTABLE ● low
202.100.128.224/27 XN-TELCOM APNIC ASSIGNED NON-PORTABLE ● low

Footprint over time

13 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-09-20

Network trust

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

NIC Handles

HJ537-AP MAINT-CHINANET-QH XP13-AP