Network · data from 2026-11-12
AS154361 ZHL-AS-AP - ZGX HK LIMITED
Registry name: ZHL-AS-AP - ZGX HK LIMITED, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS154361, 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.
| 213.109.168.0/24 | Invalid: origin | Other origin only | 4 1%low visibility |
| 181.41.200.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
AS-SET
AS154361 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 7 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 213.109.168.0/24 | ROAs covering it name AS834, AS61317, not AS154361. If AS154361 should announce it, add a ROA for AS154361. |
| Route object: none | 213.109.168.0/24 | Route objects for it name AS834, AS61317. Add a route object with origin AS154361 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS154361 whose prefix no peer sees AS154361 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.151.196.0/24 | ARIN, RADB | Valid |
| 82.47.24.0/23 | RADB, RIPE | Valid |
| 134.122.245.0/24 | APNIC | Valid |
| 134.122.254.0/24 | APNIC | Valid |
| 137.220.150.0/24 | 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.