bgpreport

Network · data from 2026-11-12

AS56019 Beijing ShuJuJia Technology Co., Ltd.

Registry name: SHUJUJIA - Beijing ShuJuJia Technology Co., Ltd., CN · PeeringDB

23IPv4 routes 87.0% RPKI valid · 39.1% with a route object
0IPv6 routes
1RPKI invalid 0 origin · 1 maxLength
2No ROA 14 with no route object for this origin
22Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS56019, seen from no peer

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 4
117.79.224.0/21 No ROA Other IRR onlyNTTCOM, RADB 44 7%low visibility 30
117.79.232.0/21 No ROA Other IRR onlyNTTCOM, RADB 44 7%low visibility 30
175.25.24.0/23 Valid Nonecovered by 175.25.0.0/16 44 7%low visibility 30
175.25.26.0/23 Valid Nonecovered by 175.25.0.0/16 44 7%low visibility 30
175.25.40.0/22 Valid Nonecovered by 175.25.0.0/16 44 7%low visibility 30
175.25.44.0/22 Valid Nonecovered by 175.25.0.0/16 44 7%low visibility 30
175.25.56.0/23 Valid Nonecovered by 175.25.0.0/16 44 7%low visibility 30
175.25.58.0/23 Valid Nonecovered by 175.25.0.0/16 44 7%low visibility 30
175.25.60.0/23 Valid Nonecovered by 175.25.0.0/16 44 7%low visibility 30
175.25.62.0/23 Valid Nonecovered by 175.25.0.0/16 44 7%low visibility 30
175.25.16.0/22 Valid Nonecovered by 175.25.0.0/16 5 1%low visibility 6
175.25.18.0/23 Valid Nonecovered by 175.25.0.0/16 5 1%low visibility 6
175.25.20.0/22 Valid Nonecovered by 175.25.0.0/16 5 1%low visibility 6
175.25.32.0/22 Valid Nonecovered by 175.25.0.0/16 5 1%low visibility 6
175.25.36.0/22 Valid Nonecovered by 175.25.0.0/16 5 1%low visibility 6
175.25.0.0/16 Valid Other IRR onlyRADB 672 100% 67
175.25.48.0/23 Valid Other IRR onlyNTTCOM, RADB 44 7%low visibility 30
175.25.50.0/23 Valid Other IRR onlyNTTCOM, RADB 44 7%low visibility 30
210.14.128.0/21 Valid Other IRR onlyNTTCOM, RADB 44 7%low visibility 30
210.14.136.0/21 Valid Other IRR onlyNTTCOM, RADB 44 7%low visibility 30
210.14.144.0/21 Valid Other IRR onlyNTTCOM, RADB 44 7%low visibility 30
210.14.152.0/21 Valid Other IRR onlyNTTCOM, RADB 44 7%low visibility 30

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
ChangePrefix or setDetailFull-table peers
ROA: maxLength175.25.16.0/23ROA 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.4 of 673
Route object: none175.25.16.0/23No 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.4 of 673
ROA: none117.79.224.0/21No ROA covers it. Add a ROA for AS56019, maxLength 21.44 of 673
Route object: RIR117.79.224.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.44 of 673
ROA: none117.79.232.0/21No ROA covers it. Add a ROA for AS56019, maxLength 21.44 of 673
Route object: RIR117.79.232.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.44 of 673
Route object: none175.25.24.0/23No 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.44 of 673
Route object: none175.25.26.0/23No 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.44 of 673
Route object: none175.25.40.0/22No 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.44 of 673
Route object: none175.25.44.0/22No 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.44 of 673
Route object: none175.25.56.0/23No 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.44 of 673
Route object: none175.25.58.0/23No 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.44 of 673
Route object: none175.25.60.0/23No 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.44 of 673
Route object: none175.25.62.0/23No 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.44 of 673
Route object: none175.25.16.0/22No 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.5 of 673
Route object: none175.25.18.0/23No 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.5 of 673
Route object: none175.25.20.0/22No 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.5 of 673
Route object: none175.25.32.0/22No 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.5 of 673
Route object: none175.25.36.0/22No 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.5 of 673
Route object: RIR175.25.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR175.25.48.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.44 of 673
Route object: RIR175.25.50.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.44 of 673
Route object: RIR210.14.128.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.44 of 673
Route object: RIR210.14.136.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.44 of 673
Route object: RIR210.14.144.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.44 of 673
Route object: RIR210.14.152.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.44 of 673

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/22NTTCOM, RADBNo ROA
122.112.64.0/22NTTCOM, RADBNo ROA
122.112.68.0/22NTTCOM, RADBNo ROA
122.112.72.0/22NTTCOM, RADBNo ROA
122.112.76.0/22NTTCOM, RADBNo ROA
122.112.80.0/22NTTCOM, RADBNo ROA
122.112.84.0/22NTTCOM, RADBNo ROA
122.112.92.0/22NTTCOM, RADBNo 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.