Network · data from 2026-11-12
AS20200 Hongshin
Registry name: DIGITAL-LAYER-APAC - Hongshin, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS20200, 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.
| 101.53.66.0/24 | No ROA | None | 672 100% |
| 101.53.69.0/24 | No ROA | Other origin only | 672 100% |
| 38.135.186.0/24 | No ROA | Nonecovered by 38.135.184.0/22 | 671 100% |
| 169.128.224.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 38.135.184.0/22 | No ROA | Other IRR onlyRADB | 670 100% |
| 169.128.224.0/24 | Valid | Nonecovered by 169.128.224.0/23 | 672 100% |
| 169.128.225.0/24 | Valid | Nonecovered by 169.128.224.0/23 | 672 100% |
| 101.53.75.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 130.12.63.0/24 | Valid | RIR databaseARIN | 672 100% |
| 45.155.255.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 45.250.221.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 45.250.222.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 45.250.223.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 2401:d860::/32 | Valid | RIR databaseAPNIC | 634 100% |
AS-SET
AS20200's PeeringDB record names no 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 19 are in fix.csv.
- ROA: none5
- Route object: none5
- Route object: RIR2
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 101.53.66.0/24 | No ROA covers it. Add a ROA for AS20200, maxLength 24. |
| Route object: none | 101.53.66.0/24 | No route object for it. Add a route object with origin AS20200 in the RIR database for the space. |
| ROA: none | 101.53.69.0/24 | No ROA covers it. Add a ROA for AS20200, maxLength 24. |
| Route object: none | 101.53.69.0/24 | Route objects for it name AS10068. Add a route object with origin AS20200 in the RIR database for the space. |
| ROA: none | 38.135.186.0/24 | No ROA covers it. Add a ROA for AS20200, maxLength 24. |
| Route object: none | 38.135.186.0/24 | No route object for it. A route object for 38.135.184.0/22 with origin AS20200 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20200 in the RIR database for the space. |
| ROA: none | 169.128.224.0/22 | No ROA covers it. Add a ROA for AS20200, maxLength 22. |
| Route object: RIR | 169.128.224.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.135.184.0/22 | No ROA covers it. Add a ROA for AS20200, maxLength 22. |
| Route object: RIR | 38.135.184.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 169.128.224.0/24 | No route object for it. A route object for 169.128.224.0/23 with origin AS20200 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20200 in the RIR database for the space. |
| Route object: none | 169.128.225.0/24 | No route object for it. A route object for 169.128.224.0/23 with origin AS20200 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20200 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS20200 whose prefix no peer sees AS20200 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 61.251.182.0/24 | APNIC | Valid |
| 115.71.26.0/24 | APNIC | Valid |
| 160.250.10.0/23 | APNIC | Valid |
| 160.250.10.0/24 | APNIC | Valid |
| 160.250.11.0/24 | APNIC | Valid |
| 169.128.224.0/23 | ARIN | Valid |
| 2602:f7b5:ff::/48 | ARIN | 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.