bgpreport

Network · data from 2026-11-12

AS63646 XJKJ

Registry name: XJKJ - Beijing Xiaoju Science and Technology Co., Ltd., CN · PeeringDB

23IPv4 routes 100.0% RPKI valid · 87.0% with a route object
7IPv6 routes 85.7% RPKI valid · 71.4% with a route object
1RPKI invalid 0 origin · 1 maxLength
0No ROA 5 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
38Route objects not announced registered with origin AS63646, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS63646, 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.

2402:840:f000::/38 Invalid: maxLength Nonecovered by 2402:840::/32 77 12% 42
103.73.48.0/24 Valid Nonecovered by 103.73.48.0/22 672 100% 67
116.85.64.0/20 Valid Nonecovered by 116.85.0.0/16 672 100% 67
116.85.240.0/20 Valid Nonecovered by 116.85.0.0/16 672 100% 67
2402:840:d000::/46 Valid Nonecovered by 2402:840::/32 636 100% 68
116.85.19.0/24 Valid Other IRR onlyRADB 673 100% 67
116.85.1.0/24 Valid Other IRR onlyRADB 672 100% 67
116.85.2.0/24 Valid Other IRR onlyRADB 672 100% 67
116.85.3.0/24 Valid Other IRR onlyRADB 672 100% 67
116.85.13.0/24 Valid Other IRR onlyRADB 672 100% 67
116.85.14.0/24 Valid Other IRR onlyRADB 672 100% 67
116.85.16.0/24 Valid Other IRR onlyRADB 672 100% 67
116.85.17.0/24 Valid Other IRR onlyRADB 672 100% 67
116.85.18.0/24 Valid Other IRR onlyRADB 672 100% 67
116.85.250.0/24 Valid Other IRR onlyRADB 672 100% 67
116.85.253.0/24 Valid Other IRR onlyRADB 672 100% 67
117.51.128.0/19 Valid Other IRR onlyRADB 672 100% 67
117.51.128.0/24 Valid Other IRR onlyRADB 672 100% 67
117.51.132.0/24 Valid Other IRR onlyRADB 672 100% 67
117.51.133.0/24 Valid Other IRR onlyRADB 672 100% 67
117.51.136.0/24 Valid Other IRR onlyRADB 672 100% 67
117.51.157.0/24 Valid Other IRR onlyRADB 672 100% 67
2402:840:d001::/48 Valid Other IRR onlyRADB 636 100% 67
2402:840:d002::/48 Valid Other IRR onlyRADB 636 100% 67
2402:840:d003::/48 Valid Other IRR onlyRADB 636 100% 67
2402:840:e000::/46 Valid Other IRR onlyRADB 636 100% 68
2402:840:e000::/48 Valid Other IRR onlyRADB 636 100% 67
117.51.130.0/24 Valid Other IRR onlyRADB 57 8%low visibility 34
116.85.0.0/18 Valid Other IRR onlyRADB 8 1%low visibility 8
116.85.0.0/16 Valid Other IRR onlyRADB 5 1%low visibility 6

AS-SET

AS63646'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 69 are in fix.csv.

  • ROA: maxLength1
  • Route object: none5
  • Route object: RIR25
  • Route object: not announced38
ChangePrefix or setDetailFull-table peers
ROA: maxLength2402:840:f000::/38ROA 2402:840::/32 AS63646 has maxLength 32; the route is a /38. Raise the maxLength, or add a ROA for 2402:840:f000::/38.77 of 636
Route object: none2402:840:f000::/38No route object for it. A route object for 2402:840::/32 with origin AS63646 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63646 in the RIR database for the space.77 of 636
Route object: none103.73.48.0/24No route object for it. A route object for 103.73.48.0/22 with origin AS63646 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63646 in the RIR database for the space.672 of 673
Route object: none116.85.64.0/20No route object for it. A route object for 116.85.0.0/16 with origin AS63646 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63646 in the RIR database for the space.672 of 673
Route object: none116.85.240.0/20No route object for it. A route object for 116.85.0.0/16 with origin AS63646 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63646 in the RIR database for the space.672 of 673
Route object: none2402:840:d000::/46No route object for it. A route object for 2402:840::/32 with origin AS63646 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63646 in the RIR database for the space.636 of 636
Route object: RIR116.85.19.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.85.1.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR116.85.2.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR116.85.3.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR116.85.13.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR116.85.14.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR116.85.16.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR116.85.17.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR116.85.18.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR116.85.250.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR116.85.253.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR117.51.128.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR117.51.128.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR117.51.132.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR117.51.133.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR117.51.136.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR117.51.157.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2402:840:d001::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2402:840:d002::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2402:840:d003::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2402:840:e000::/46Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2402:840:e000::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR117.51.130.0/24Route object only in RADB. Add it in the RIR database for the space.57 of 673
Route object: RIR116.85.0.0/18Route object only in RADB. Add it in the RIR database for the space.8 of 673
Route object: RIR116.85.0.0/16Route object only in RADB. Add it in the RIR database for the space.5 of 673

Route objects not announced

Route objects with origin AS63646 whose prefix no peer sees AS63646 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.73.48.0/22RADBValid
116.85.0.0/24RADBValid
116.85.4.0/24RADBValid
116.85.5.0/24RADBValid
116.85.6.0/24RADBValid
116.85.7.0/24RADBValid
116.85.8.0/24RADBValid
116.85.9.0/24RADBValid
116.85.10.0/24RADBValid
116.85.11.0/24RADBValid
116.85.12.0/24RADBValid
116.85.15.0/24RADBValid
116.85.20.0/24RADBValid
116.85.21.0/24RADBValid
116.85.22.0/24RADBValid
116.85.23.0/24RADBValid
116.85.248.0/24RADBValid
116.85.249.0/24RADBValid
116.85.251.0/24RADBValid
116.85.252.0/24RADBValid
116.85.254.0/24RADBValid
116.85.255.0/24RADBValid
117.51.129.0/24RADBValid
117.51.131.0/24RADBValid
117.51.134.0/24RADBValid
117.51.135.0/24RADBValid
117.51.137.0/24RADBValid
117.51.138.0/24RADBValid
117.51.139.0/24RADBValid
117.51.140.0/24RADBValid
117.51.141.0/24RADBValid
117.51.142.0/24RADBValid
117.51.143.0/24RADBValid
2402:840::/32RADBValid
2402:840:d000::/48RADBValid
2402:840:e001::/48RADBValid
2402:840:e002::/48RADBValid
2402:840:e003::/48RADBValid

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.