Network · data from 2026-11-12
AS56019 Beijing ShuJuJia Technology Co., Ltd.
Registry name: SHUJUJIA - Beijing ShuJuJia Technology Co., Ltd., CN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS56019, 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.
| 175.25.16.0/23 | Invalid: maxLength | Nonecovered by 175.25.0.0/16 | 4 1%low visibility |
| 117.79.224.0/21 | No ROA | Other IRR onlyNTTCOM, RADB | 44 7%low visibility |
| 117.79.232.0/21 | No ROA | Other IRR onlyNTTCOM, RADB | 44 7%low visibility |
| 175.25.24.0/23 | Valid | Nonecovered by 175.25.0.0/16 | 44 7%low visibility |
| 175.25.26.0/23 | Valid | Nonecovered by 175.25.0.0/16 | 44 7%low visibility |
| 175.25.40.0/22 | Valid | Nonecovered by 175.25.0.0/16 | 44 7%low visibility |
| 175.25.44.0/22 | Valid | Nonecovered by 175.25.0.0/16 | 44 7%low visibility |
| 175.25.56.0/23 | Valid | Nonecovered by 175.25.0.0/16 | 44 7%low visibility |
| 175.25.58.0/23 | Valid | Nonecovered by 175.25.0.0/16 | 44 7%low visibility |
| 175.25.60.0/23 | Valid | Nonecovered by 175.25.0.0/16 | 44 7%low visibility |
| 175.25.62.0/23 | Valid | Nonecovered by 175.25.0.0/16 | 44 7%low visibility |
| 175.25.16.0/22 | Valid | Nonecovered by 175.25.0.0/16 | 5 1%low visibility |
| 175.25.18.0/23 | Valid | Nonecovered by 175.25.0.0/16 | 5 1%low visibility |
| 175.25.20.0/22 | Valid | Nonecovered by 175.25.0.0/16 | 5 1%low visibility |
| 175.25.32.0/22 | Valid | Nonecovered by 175.25.0.0/16 | 5 1%low visibility |
| 175.25.36.0/22 | Valid | Nonecovered by 175.25.0.0/16 | 5 1%low visibility |
| 175.25.0.0/16 | Valid | Other IRR onlyRADB | 672 100% |
| 175.25.48.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 44 7%low visibility |
| 175.25.50.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 44 7%low visibility |
| 210.14.128.0/21 | Valid | Other IRR onlyNTTCOM, RADB | 44 7%low visibility |
| 210.14.136.0/21 | Valid | Other IRR onlyNTTCOM, RADB | 44 7%low visibility |
| 210.14.144.0/21 | Valid | Other IRR onlyNTTCOM, RADB | 44 7%low visibility |
| 210.14.152.0/21 | Valid | Other IRR onlyNTTCOM, RADB | 44 7%low visibility |
AS-SET
AS56019's PeeringDB record names no 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 34 are in fix.csv.
- ROA: maxLength1
- ROA: none2
- Route object: none14
- Route object: RIR9
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 175.25.16.0/23 | ROA 175.25.0.0/16 AS56019 has maxLength 16; ROA 175.25.16.0/21 AS56019 has maxLength 21; ROA 175.25.16.0/22 AS56019 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 175.25.16.0/23. |
| Route object: none | 175.25.16.0/23 | No route object for it. A route object for 175.25.0.0/16 with origin AS56019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56019 in the RIR database for the space. |
| ROA: none | 117.79.224.0/21 | No ROA covers it. Add a ROA for AS56019, maxLength 21. |
| Route object: RIR | 117.79.224.0/21 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 117.79.232.0/21 | No ROA covers it. Add a ROA for AS56019, maxLength 21. |
| Route object: RIR | 117.79.232.0/21 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: none | 175.25.24.0/23 | No route object for it. A route object for 175.25.0.0/16 with origin AS56019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56019 in the RIR database for the space. |
| Route object: none | 175.25.26.0/23 | No route object for it. A route object for 175.25.0.0/16 with origin AS56019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56019 in the RIR database for the space. |
| Route object: none | 175.25.40.0/22 | No route object for it. A route object for 175.25.0.0/16 with origin AS56019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56019 in the RIR database for the space. |
| Route object: none | 175.25.44.0/22 | No route object for it. A route object for 175.25.0.0/16 with origin AS56019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56019 in the RIR database for the space. |
| Route object: none | 175.25.56.0/23 | No route object for it. A route object for 175.25.0.0/16 with origin AS56019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56019 in the RIR database for the space. |
| Route object: none | 175.25.58.0/23 | No route object for it. A route object for 175.25.0.0/16 with origin AS56019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56019 in the RIR database for the space. |
| Route object: none | 175.25.60.0/23 | No route object for it. A route object for 175.25.0.0/16 with origin AS56019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56019 in the RIR database for the space. |
| Route object: none | 175.25.62.0/23 | No route object for it. A route object for 175.25.0.0/16 with origin AS56019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56019 in the RIR database for the space. |
| Route object: none | 175.25.16.0/22 | No route object for it. A route object for 175.25.0.0/16 with origin AS56019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56019 in the RIR database for the space. |
| Route object: none | 175.25.18.0/23 | No route object for it. A route object for 175.25.0.0/16 with origin AS56019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56019 in the RIR database for the space. |
| Route object: none | 175.25.20.0/22 | No route object for it. A route object for 175.25.0.0/16 with origin AS56019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56019 in the RIR database for the space. |
| Route object: none | 175.25.32.0/22 | No route object for it. A route object for 175.25.0.0/16 with origin AS56019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56019 in the RIR database for the space. |
| Route object: none | 175.25.36.0/22 | No route object for it. A route object for 175.25.0.0/16 with origin AS56019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56019 in the RIR database for the space. |
| Route object: RIR | 175.25.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 175.25.48.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 175.25.50.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.14.128.0/21 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.14.136.0/21 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.14.144.0/21 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.14.152.0/21 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS56019 whose prefix no peer sees AS56019 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 121.101.216.0/22 | NTTCOM, RADB | No ROA |
| 122.112.64.0/22 | NTTCOM, RADB | No ROA |
| 122.112.68.0/22 | NTTCOM, RADB | No ROA |
| 122.112.72.0/22 | NTTCOM, RADB | No ROA |
| 122.112.76.0/22 | NTTCOM, RADB | No ROA |
| 122.112.80.0/22 | NTTCOM, RADB | No ROA |
| 122.112.84.0/22 | NTTCOM, RADB | No ROA |
| 122.112.92.0/22 | NTTCOM, 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.