Network · data from 2026-11-12
AS9803 JINGXUN - Beijing Jingxun Public Information Technology Co., Ltd
Registry name: JINGXUN - Beijing Jingxun Public Information Technology Co., Ltd, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9803, 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.
| 211.150.124.0/24 | Valid | Nonecovered by 211.150.124.0/23 | 672 100% |
| 211.150.98.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 211.150.100.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 211.150.122.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 211.150.124.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 211.150.128.0/24 | Valid | RIR databaseAPNIC | 672 100% |
AS-SET
AS9803 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 14 are in fix.csv.
- Route object: none1
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 211.150.124.0/24 | No route object for it. A route object for 211.150.124.0/23 with origin AS9803 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9803 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9803 whose prefix no peer sees AS9803 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 119.61.0.0/16 | RADB | No ROA |
| 119.61.0.0/17 | APNIC | Invalid: origin |
| 139.176.0.0/16 | APNIC, RADB | Valid |
| 210.78.128.0/22 | APNIC, RADB | Valid |
| 211.99.224.0/19 | APNIC, RADB | Valid |
| 211.150.0.0/16 | APNIC, NTTCOM, RADB | No ROA |
| 211.150.0.0/17 | APNIC | Valid |
| 211.150.128.0/18 | APNIC | Valid |
| 211.154.96.0/19 | RADB | No ROA |
| 211.157.128.0/18 | APNIC | Invalid: origin |
| 211.157.192.0/20 | APNIC | Invalid: origin |
| 211.157.224.0/19 | APNIC | Invalid: origin |
| 2402:b200::/32 | 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.