No.31, Jin-rong Street

NC-TELECOM-COMPANY
BGP inherited
Cluster stats
Netblocks3
All fragments 4 blocks across 2 clusters
Cluster ID206466753
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

IP Ranges (3)

⬇ export CSV
CIDR Org name Registry Status Confidence
202.101.194.0/25 NC-TELECOM-COMPANY APNIC ASSIGNED NON-PORTABLE ● low
202.101.240.208/28 NC-TELECOM-COMPANY APNIC ASSIGNED NON-PORTABLE ● low
202.101.243.224/27 NC-TELECOM-COMPANY APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “NC TELECOM” — 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.

Network trust

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

NIC Handles

MAINT-IP-WWF WZ1-CN XY1-AP