bgpreport

Network · data from 2026-11-12

AS131486 Beijing Jingdong 360 Degree E-commerce

Registry name: JDCOM - Beijing Jingdong 360 Degree E-commerce Co., Ltd., CN · PeeringDB

9IPv4 routes 100.0% RPKI valid · 88.9% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 1 with no route object for this origin
10Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS131486, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS131486, 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.
116.198.80.0/21 Valid Other origin only 4 1%low visibility 5
101.124.0.0/16 Valid Other IRR onlyRADB 5 1%low visibility 6
101.124.0.0/18 Valid Other IRR onlyRADB 5 1%low visibility 6
101.124.64.0/18 Valid Other IRR onlyRADB 5 1%low visibility 6
101.124.128.0/19 Valid Other IRR onlyRADB 5 1%low visibility 6
103.224.220.0/22 Valid Other IRR onlyRADB 5 1%low visibility 6
114.67.128.0/17 Valid Other IRR onlyRADB 5 1%low visibility 6
114.67.128.0/19 Valid Other IRR onlyRADB 5 1%low visibility 6
117.72.248.0/22 Valid Other IRR onlyRADB 5 1%low visibility 6
2402:db40::/33 Valid Other IRR onlyRADB 3 0%low visibility 3

AS-SET

AS131486'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 19 are in fix.csv.

  • Route object: none1
  • Route object: RIR9
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
Route object: none116.198.80.0/21Route objects for it name AS23724. Add a route object with origin AS131486 in the RIR database for the space.4 of 673
Route object: RIR101.124.0.0/16Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR101.124.0.0/18Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR101.124.64.0/18Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR101.124.128.0/19Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR103.224.220.0/22Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR114.67.128.0/17Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR114.67.128.0/19Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR117.72.248.0/22Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR2402:db40::/33Route object only in RADB. Add it in the RIR database for the space.3 of 636

Route objects not announced

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

101.124.24.0/21RADBValid
101.124.160.0/19RADBValid
114.67.160.0/19RADBValid
114.67.192.0/19RADBValid
116.198.0.0/18RADBValid
2402:db40::/32APNICValid
2402:db40:3110::/44RADBValid
2402:db40:4110::/44RADBValid
2403:1ec0::/32APNICInvalid: origin

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.