bgpreport

Network · data from 2026-11-12

AS17929 JPMC-AP - JPMorgan Chase APTI

Registry name: JPMC-AP - JPMorgan Chase APTI, US · not in PeeringDB

3IPv4 routes 66.7% RPKI valid · 66.7% with a route object
3IPv6 routes 66.7% RPKI valid · 66.7% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
17Route objects not announced registered with origin AS17929, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS17929, 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.160.0/19 No ROA None 673 100% 67
2407:e500:60::/43 No ROA None 633 100% 69
161.121.160.0/20 Valid RIR databaseARIN 673 100% 67
161.121.176.0/20 Valid RIR databaseARIN 673 100% 67
2407:e500:60::/47 Valid RIR databaseAPNIC 635 100% 68
2407:e500:70::/47 Valid RIR databaseAPNIC 635 100% 68

AS-SET

AS17929 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 21 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: none161.121.160.0/19No ROA covers it. Add a ROA for AS17929, maxLength 19.673 of 673
Route object: none161.121.160.0/19No route object for it. Add a route object with origin AS17929 in the RIR database for the space.673 of 673
ROA: none2407:e500:60::/43No ROA covers it. Add a ROA for AS17929, maxLength 43.633 of 636
Route object: none2407:e500:60::/43No route object for it. Add a route object with origin AS17929 in the RIR database for the space.633 of 636

Route objects not announced

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

103.246.196.0/22APNICValid
103.246.196.0/23APNICInvalid: maxLength
103.246.196.0/24APNICValid
103.246.197.0/24APNICValid
103.246.198.0/24APNICValid
103.246.199.0/24APNICValid
170.148.64.0/21RADBNo ROA
170.148.96.0/19RADB, REACHNo ROA
170.148.128.0/21RADBNo ROA
170.148.136.0/22RADB, REACHNo ROA
199.253.242.0/24RADBNo ROA
199.253.247.0/24RADBNo ROA
204.86.14.0/23ARINInvalid: origin
2407:e500::/47APNICValid
2407:e500:2::/47APNICValid
2407:e500:4::/47APNICValid
2407:e500:6::/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.