Network · data from 2026-11-12
AS138542 ZTINFO-AS-HK - ZT Information Network Co., Limited
Registry name: ZTINFO-AS-HK - ZT Information Network Co., Limited, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS138542, 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.
| 79.109.48.0/20 | No ROA | RIR databaseAPNIC | 1 0%low visibility |
| 79.109.0.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 79.109.7.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 79.109.64.0/18 | Valid | RIR databaseAPNIC | 673 100% |
| 79.109.240.0/21 | Valid | RIR databaseAPNIC | 672 100% |
| 79.109.128.0/18 | Valid | RIR databaseAPNIC | 60 9%low visibility |
| 79.109.192.0/19 | Valid | RIR databaseAPNIC | 60 9%low visibility |
AS-SET
AS138542 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 4 are in fix.csv.
- ROA: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 79.109.48.0/20 | No ROA covers it. Add a ROA for AS138542, maxLength 20. |
Route objects not announced
Route objects with origin AS138542 whose prefix no peer sees AS138542 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 79.109.36.0/22 | APNIC | Invalid: origin |
| 79.109.240.0/22 | APNIC | Valid |
| 79.109.244.0/22 | APNIC | Valid |
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.