Network · data from 2026-11-12
AS4611 xinhuanet - CNNIC member
Registry name: xinhuanet - CNNIC member, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS4611, 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.
| 103.66.32.0/22 | No ROA | RIR databaseAPNIC | 672 100% |
| 103.228.136.0/22 | No ROA | RIR databaseAPNIC | 672 100% |
| 203.192.6.0/24 | Valid | Nonecovered by 203.192.6.0/23 | 672 100% |
| 203.192.7.0/24 | Valid | Nonecovered by 203.192.6.0/23 | 672 100% |
| 203.192.8.0/24 | Valid | Nonecovered by 203.192.8.0/23 | 672 100% |
| 203.192.9.0/24 | Valid | Nonecovered by 203.192.8.0/23 | 672 100% |
| 202.108.119.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.123.107.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.123.110.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.192.1.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.192.2.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.192.4.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.192.10.0/24 | Valid | RIR databaseAPNIC | 672 100% |
AS-SET
AS4611 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 24 are in fix.csv.
- ROA: none2
- Route object: none4
- Route object: not announced18
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.66.32.0/22 | No ROA covers it. Add a ROA for AS4611, maxLength 22. |
| ROA: none | 103.228.136.0/22 | No ROA covers it. Add a ROA for AS4611, maxLength 22. |
| Route object: none | 203.192.6.0/24 | No route object for it. A route object for 203.192.6.0/23 with origin AS4611 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4611 in the RIR database for the space. |
| Route object: none | 203.192.7.0/24 | No route object for it. A route object for 203.192.6.0/23 with origin AS4611 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4611 in the RIR database for the space. |
| Route object: none | 203.192.8.0/24 | No route object for it. A route object for 203.192.8.0/23 with origin AS4611 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4611 in the RIR database for the space. |
| Route object: none | 203.192.9.0/24 | No route object for it. A route object for 203.192.8.0/23 with origin AS4611 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4611 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS4611 whose prefix no peer sees AS4611 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.84.0.0/20 | NTTCOM, RADB | No ROA |
| 202.84.0.0/21 | NTTCOM, RADB | No ROA |
| 202.84.0.0/22 | NTTCOM | No ROA |
| 202.84.1.0/24 | NTTCOM, RADB | No ROA |
| 202.84.2.0/24 | RADB | No ROA |
| 202.84.3.0/24 | RADB | No ROA |
| 202.84.5.0/24 | NTTCOM, RADB | No ROA |
| 202.84.6.0/24 | NTTCOM, RADB | No ROA |
| 202.84.7.0/24 | NTTCOM, RADB | No ROA |
| 202.84.9.0/24 | NTTCOM, RADB | No ROA |
| 202.84.12.0/22 | NTTCOM | No ROA |
| 202.84.12.0/23 | RADB | No ROA |
| 202.84.12.0/24 | NTTCOM, RADB | No ROA |
| 202.84.13.0/24 | NTTCOM | No ROA |
| 202.84.14.0/24 | NTTCOM | No ROA |
| 202.84.15.0/24 | NTTCOM | No ROA |
| 203.192.6.0/23 | APNIC | No ROA |
| 203.192.8.0/23 | 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.