NET-JP-Chunghwa-Telecom-Japan
Data as of 2026-08-09
BGP inherited
Cluster stats
| Netblocks | 3 |
| All fragments | 5 blocks across 2 clusters |
| Cluster ID | 217912178 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| 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 · report an issue | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 27.110.7.208/29 | NET-JP-Chunghwa-Telecom-Japan | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 27.110.16.40/29 | NET-JP-Chunghwa-Telecom-Japan | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 148.109.38.40/29 | NET-JP-Chunghwa-Telecom-Japan | APNIC | ASSIGNED NON-PORTABLE | ● high |
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
AC2582-AP
MAINT-CTSCL-JP
SH2517-AP
SH2517-AP
VC287-AP
VC287-AP
WMC29-AP
WMC29-AP