TAIZHOU-TELECOM-CLIENT-DEP
BGP inherited
Cluster stats
| Netblocks | 3 |
| All fragments | 4 blocks across 2 clusters |
| Cluster ID | 206520720 |
| Registry | APNIC |
| Customers | find 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 |
|---|---|---|---|---|
| 60.191.185.0/29 | TAIZHOU-TELECOM-CLIENT-DEP | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 61.175.218.8/29 | TAIZHOU-TELECOM-CLIENT-DEP | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 122.226.140.128/29 | TAIZHOU-TELECOM-CLIENT-DEP | APNIC | ASSIGNED NON-PORTABLE | ● high |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “TAIZHOU TELECOM CLIENT” — 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.
- TAIZHOU-TELECOM-CLIENT-DEPT 1 blocks
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
CT24-AP
CY802-AP
MAINT-CN-CHINANET-ZJ-TZ