TBC-TW
BGP inherited
Cluster stats
| Netblocks | 5 |
| All fragments | 814 blocks across 8 clusters |
| Cluster ID | 191848166 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 61.58.64.0/20 | TBC-TW | APNIC | ALLOCATED PORTABLE | ● low |
| 61.58.80.0/20 | TBC-TW | APNIC | ALLOCATED PORTABLE | ● low |
| 61.58.160.0/19 | TBC-TW | APNIC | ALLOCATED PORTABLE | ● low |
| 61.63.96.0/19 | TBC-TW | APNIC | ALLOCATED PORTABLE | ● low |
| 202.148.214.0/23 | TBC-TW | APNIC | ALLOCATED PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
80.0%
of checked blocks have valid RPKI ROA coverage
(4 of 5)
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
MAINT-TW-TWNIC