bgpreport

Network · data from 2026-11-12

AS32066 JPMORGAN-DALLAS-JIP - JPMorgan Chase & Co.

Registry name: JPMORGAN-DALLAS-JIP - JPMorgan Chase & Co., US · not in PeeringDB

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

Announced routes

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

170.148.240.0/21 No ROA None 673 100% 67
2a04:ec10::/47 No ROA None 635 100% 67
170.148.192.0/19 No ROA Other IRR onlyRADB 673 100% 67
199.253.241.0/24 No ROA Other IRR onlyRADB 673 100% 67
170.148.208.0/20 No ROA Other IRR onlyRADB 672 100% 67
199.253.246.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS32066 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 17 are in fix.csv.

  • ROA: none6
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none170.148.240.0/21No ROA covers it. Add a ROA for AS32066, maxLength 21.673 of 673
Route object: none170.148.240.0/21No route object for it. Add a route object with origin AS32066 in the RIR database for the space.673 of 673
ROA: none2a04:ec10::/47No ROA covers it. Add a ROA for AS32066, maxLength 47.635 of 636
Route object: none2a04:ec10::/47No route object for it. Add a route object with origin AS32066 in the RIR database for the space.635 of 636
ROA: none170.148.192.0/19No ROA covers it. Add a ROA for AS32066, maxLength 19.673 of 673
Route object: RIR170.148.192.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none199.253.241.0/24No ROA covers it. Add a ROA for AS32066, maxLength 24.673 of 673
Route object: RIR199.253.241.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none170.148.208.0/20No ROA covers it. Add a ROA for AS32066, maxLength 20.672 of 673
Route object: RIR170.148.208.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none199.253.246.0/24No ROA covers it. Add a ROA for AS32066, maxLength 24.672 of 673
Route object: RIR199.253.246.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

170.148.60.0/22ARINNo ROA
170.148.60.0/23ARINNo ROA
170.148.62.0/23ARINNo ROA
170.148.200.0/22ARINNo ROA
204.86.14.0/23ARINInvalid: 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.