bgpreport

Network · data from 2026-11-12

AS38551 JPMORGAN-TRANSIT-AS-AU - JPMORGAN Australia

Registry name: JPMORGAN-TRANSIT-AS-AU - JPMORGAN Australia, US · not in PeeringDB

7IPv4 routes 57.1% RPKI valid · 85.7% with a route object
4IPv6 routes 50.0% RPKI valid · 75.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No ROA 2 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS38551, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38551, 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.
161.121.208.0/20 No ROA None 672 100% 67
2407:e500:80::/43 No ROA None 0 0%low visibility 2
170.148.144.0/23 No ROA Other IRR onlyNTTCOM 672 100% 67
161.121.192.0/20 No ROA Other IRR onlyNTTCOM 671 100% 67
2407:e500:c::/46 No ROA Other IRR onlyRADB 632 99% 68
161.121.192.0/21 Valid RIR databaseARIN, RADB 673 100% 67
161.121.208.0/21 Valid RIR databaseARIN 673 100% 67
161.121.216.0/21 Valid RIR databaseARIN 673 100% 66
161.121.200.0/21 Valid RIR databaseARIN, RADB 670 100% 67
2407:e500:c::/47 Valid RIR databaseAPNIC, NTTCOM 635 100% 67
2407:e500:e::/47 Valid RIR databaseAPNIC, NTTCOM 633 100% 68

AS-SET

AS38551 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 16 are in fix.csv.

  • ROA: none5
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none161.121.208.0/20No ROA covers it. Add a ROA for AS38551, maxLength 20.672 of 673
Route object: none161.121.208.0/20No route object for it. Add a route object with origin AS38551 in the RIR database for the space.672 of 673
ROA: none2407:e500:80::/43No ROA covers it. Add a ROA for AS38551, maxLength 43.0 of 636
Route object: none2407:e500:80::/43No route object for it. Add a route object with origin AS38551 in the RIR database for the space.0 of 636
ROA: none170.148.144.0/23No ROA covers it. Add a ROA for AS38551, maxLength 23.672 of 673
Route object: RIR170.148.144.0/23Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none161.121.192.0/20No ROA covers it. Add a ROA for AS38551, maxLength 20.671 of 673
Route object: RIR161.121.192.0/20Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none2407:e500:c::/46No ROA covers it. Add a ROA for AS38551, maxLength 46.632 of 636
Route object: RIR2407:e500:c::/46Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

2407:e500:10::/47APNICValid
2407:e500:12::/47APNICValid
2407:e500:80::/47APNICValid
2407:e500:90::/47APNICValid
2407:e500:a0::/47APNICValid
2407:e500:b0::/47APNICValid

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.