Network · data from 2026-11-12
AS209650 Wu Zhiyuan
Registry name: ZHIYUAN-AS Wu Zhiyuan, CN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS209650, 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.
| 2a0e:b107:31::/48 | No ROA | Nonecovered by 2a0e:b107:30::/44 | 2 0%low visibility |
| 44.32.157.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 2a0e:b107:33::/48 | No ROA | RIR databaseRIPE | 635 100% |
| 2a0e:b107:30::/48 | No ROA | RIR databaseRIPE | 634 100% |
| 2a0e:b107:32::/48 | No ROA | RIR databaseRIPE | 634 100% |
| 2a0d:2687::/32 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS209650: AS-ZHIYUAN. 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 (AS209650 isn't in the set, or no route object for AS209650 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 | AS209650 in it | Not covered |
|---|---|---|---|---|---|
| AS-ZHIYUAN | RIPE | 1 | 1 | Yes | 0 |
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 15 are in fix.csv.
- ROA: none5
- Route object: none1
- Route object: RIR1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a0e:b107:31::/48 | No ROA covers it. Add a ROA for AS209650, maxLength 48. |
| Route object: none | 2a0e:b107:31::/48 | No route object for it. A route object for 2a0e:b107:30::/44 with origin AS209650 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209650 in the RIR database for the space. |
| ROA: none | 44.32.157.0/24 | No ROA covers it. Add a ROA for AS209650, maxLength 24. |
| Route object: RIR | 44.32.157.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2a0e:b107:33::/48 | No ROA covers it. Add a ROA for AS209650, maxLength 48. |
| ROA: none | 2a0e:b107:30::/48 | No ROA covers it. Add a ROA for AS209650, maxLength 48. |
| ROA: none | 2a0e:b107:32::/48 | No ROA covers it. Add a ROA for AS209650, maxLength 48. |
Route objects not announced
Route objects with origin AS209650 whose prefix no peer sees AS209650 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.144.109.0/24 | RADB | No ROA |
| 2401:f860:200::/48 | APNIC | Valid |
| 2405:84c0:fcf0::/48 | APNIC | Valid |
| 2602:fed2:7302::/48 | ALTDB, ARIN, RADB | Valid |
| 2602:feda:2e0::/44 | ALTDB, ARIN, RADB | No ROA |
| 2a07:1c44:8100::/40 | ALTDB | Invalid: origin |
| 2a0c:5440:80::/44 | RADB | No ROA |
| 2a0e:b107:30::/44 | RADB, RIPE | 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.