Network · data from 2026-11-12
AS17781 XHNEWS - XINHUA NEWS AGENCY
Registry name: XHNEWS - XINHUA NEWS AGENCY, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17781, 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.
| 203.192.24.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.192.12.0/22 | No ROA | RIR databaseAPNIC | 673 100% |
| 202.84.17.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.123.96.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.123.98.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.123.108.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 203.192.16.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.123.106.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.123.111.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.192.3.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.192.5.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.192.11.0/24 | Valid | RIR databaseAPNIC | 673 100% |
AS-SET
AS17781 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 17 are in fix.csv.
- ROA: none2
- Route object: RIR6
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.192.24.0/23 | No ROA covers it. Add a ROA for AS17781, maxLength 23. |
| Route object: RIR | 203.192.24.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.192.12.0/22 | No ROA covers it. Add a ROA for AS17781, maxLength 22. |
| Route object: RIR | 202.84.17.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.123.96.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.123.98.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.123.108.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.192.16.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17781 whose prefix no peer sees AS17781 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.84.0.0/22 | APNIC | No ROA |
| 202.84.16.0/23 | APNIC | No ROA |
| 202.123.96.0/20 | APNIC, NTTCOM, RADB | No ROA |
| 202.123.96.0/21 | APNIC | No ROA |
| 202.123.104.0/23 | APNIC | No ROA |
| 202.123.108.0/23 | APNIC | No ROA |
| 203.192.0.0/19 | APNIC, NTTCOM, RADB | No ROA |
| 203.192.0.0/24 | APNIC | No ROA |
| 203.192.16.0/20 | APNIC | No ROA |
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.