bgpreport

Network · data from 2026-11-12

AS7743 JPMorgan Chase

Registry name: JPMORGAN-AS7743 - JPMorgan Chase & Co., US · PeeringDB

8IPv4 routes 25.0% RPKI valid · 12.5% with a route object
4IPv6 routes 0.0% RPKI valid · 75.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
10No ROA 8 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS7743, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS7743, 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.
159.53.0.0/16 No ROA Other origin only 673 100% 67
159.53.64.0/19 No ROA None 673 100% 67
199.253.244.0/23 No ROA None 673 100% 67
2620:11::/45 No ROA None 635 100% 67
159.53.32.0/19 No ROA None 2 0%low visibility 2
198.27.1.0/24 No ROA None 2 0%low visibility 2
199.253.244.0/24 No ROA None 2 0%low visibility 2
2620:11:8::/47 No ROA RIR databaseARIN 636 100% 67
2620:11:2::/47 No ROA RIR databaseARIN 635 100% 67
2620:11::/47 No ROA RIR databaseARIN 1 0%low visibility 1
209.211.208.0/22 Valid None 672 100% 67
159.53.16.0/20 Valid RIR databaseARIN 673 100% 67

AS-SET

AS7743'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 26 are in fix.csv.

  • ROA: none10
  • Route object: none8
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none159.53.0.0/16No ROA covers it. Add a ROA for AS7743, maxLength 16.673 of 673
Route object: none159.53.0.0/16Route objects for it name AS10934. Add a route object with origin AS7743 in the RIR database for the space.673 of 673
ROA: none159.53.64.0/19No ROA covers it. Add a ROA for AS7743, maxLength 19.673 of 673
Route object: none159.53.64.0/19No route object for it. Add a route object with origin AS7743 in the RIR database for the space.673 of 673
ROA: none199.253.244.0/23No ROA covers it. Add a ROA for AS7743, maxLength 23.673 of 673
Route object: none199.253.244.0/23No route object for it. Add a route object with origin AS7743 in the RIR database for the space.673 of 673
ROA: none2620:11::/45No ROA covers it. Add a ROA for AS7743, maxLength 45.635 of 636
Route object: none2620:11::/45No route object for it. Add a route object with origin AS7743 in the RIR database for the space.635 of 636
ROA: none159.53.32.0/19No ROA covers it. Add a ROA for AS7743, maxLength 19.2 of 673
Route object: none159.53.32.0/19No route object for it. Add a route object with origin AS7743 in the RIR database for the space.2 of 673
ROA: none198.27.1.0/24No ROA covers it. Add a ROA for AS7743, maxLength 24.2 of 673
Route object: none198.27.1.0/24No route object for it. Add a route object with origin AS7743 in the RIR database for the space.2 of 673
ROA: none199.253.244.0/24No ROA covers it. Add a ROA for AS7743, maxLength 24.2 of 673
Route object: none199.253.244.0/24No route object for it. Add a route object with origin AS7743 in the RIR database for the space.2 of 673
ROA: none2620:11:8::/47No ROA covers it. Add a ROA for AS7743, maxLength 47.636 of 636
ROA: none2620:11:2::/47No ROA covers it. Add a ROA for AS7743, maxLength 47.635 of 636
ROA: none2620:11::/47No ROA covers it. Add a ROA for AS7743, maxLength 47.1 of 636
Route object: none209.211.208.0/22No route object for it. Add a route object with origin AS7743 in the RIR database for the space.672 of 673

Route objects not announced

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

159.53.96.0/19RADBNo ROA
159.53.160.0/19RADBNo ROA
159.53.198.0/23RADBNo ROA
159.53.206.0/24RADBNo ROA
159.53.216.0/24RADBNo ROA
199.253.245.0/24RADBNo ROA
2620:11:4::/47ARINNo ROA
2620:11:6::/47ARINNo 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.