TBCOM-NET
Cluster stats
| Netblocks | 7 |
| Cluster ID | 193030493 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 8 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
7
0 netblocks since 2026-07-05
2026-07-05
peak 7
2026-07-06
IP Ranges (7)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 59.102.128.0/17 | TBCOM-NET | APNIC | ALLOCATED PORTABLE | ● low |
| 61.57.64.0/18 | TBCOM-NET | APNIC | ALLOCATED PORTABLE | ● low |
| 116.241.0.0/16 | TBCOM-NET | APNIC | ALLOCATED PORTABLE | ● low |
| 123.0.192.0/18 | TBCOM-NET | APNIC | ALLOCATED PORTABLE | ● low |
| 123.110.0.0/16 | TBCOM-NET | APNIC | ALLOCATED PORTABLE | ● low |
| 123.240.0.0/15 | TBCOM-NET | APNIC | ALLOCATED PORTABLE | ● low |
| 2405:9200::/32 | TBCOM-NET | APNIC | ALLOCATED PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(7 of 7)
RPKI-inferred operator
Asia Pacific Telecom
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
AT939-AP
HN8-AP
HN8-AP
HS2369-AP
HS2369-AP
MAINT-TW-TWNIC
tNA5-AP
tNA5-AP