Network · data from 2026-11-12
AS23911 CNGI-6IX
Registry name: CNGI-BJIX-AS-AP - China Next Generation Internet Beijing IX, CN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23911, 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.
| 2001:252::/32 | No ROA | Other origin only | 73 11% |
| 210.25.187.0/24 | No ROA | None | 16 2%low visibility |
| 210.25.189.0/24 | No ROA | None | 16 2%low visibility |
AS-SET
PeeringDB's irr_as_set for AS23911: AS4538:AS-CUSTOMERS-V6. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS23911 isn't in the set, or no route object for AS23911 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS23911 in it | Not covered |
|---|---|---|---|---|---|
| AS4538:AS-CUSTOMERS-V6 | APNIC | 4,297 | 11 | Yes | 3 |
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 10 are in fix.csv.
- ROA: none3
- Route object: none3
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2001:252::/32 | No ROA covers it. Add a ROA for AS23911, maxLength 32. |
| Route object: none | 2001:252::/32 | Route objects for it name AS4538. Add a route object with origin AS23911 in the RIR database for the space. |
| ROA: none | 210.25.187.0/24 | No ROA covers it. Add a ROA for AS23911, maxLength 24. |
| Route object: none | 210.25.187.0/24 | No route object for it. Add a route object with origin AS23911 in the RIR database for the space. |
| ROA: none | 210.25.189.0/24 | No ROA covers it. Add a ROA for AS23911, maxLength 24. |
| Route object: none | 210.25.189.0/24 | No route object for it. Add a route object with origin AS23911 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS23911 whose prefix no peer sees AS23911 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.38.108.0/24 | RADB | No ROA |
| 202.38.109.0/24 | RADB | No ROA |
| 202.38.118.0/24 | RADB | No ROA |
| 202.38.122.0/24 | RADB | 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.