Network · data from 2026-11-12
AS216224 Tianjin Tianzhan Technology Co., Ltd.
Registry name: Tianjin-Tianzhan-Technology-Co-Ltd Tianjin Tianzhan Technology Co., Ltd., CN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS216224, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 151.247.163.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 191.44.75.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 82.21.50.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 82.39.172.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 178.83.109.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
AS-SET
AS216224's PeeringDB record names no AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS216224 is announced.
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.