bgpreport

Network · data from 2026-11-12

AS38910 JPMORGAN-TRANSIT-AS-JP-AP - Transit AS Tokyo

Registry name: JPMORGAN-TRANSIT-AS-JP-AP - Transit AS Tokyo, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38910, 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.130.0/24 Invalid: maxLength Nonecovered by 161.121.128.0/20 135 20% 53
161.121.135.0/24 Invalid: maxLength Nonecovered by 161.121.128.0/20 135 20% 53
161.121.144.0/20 Valid RIR databaseAPNIC 672 100% 67
161.121.128.0/19 Valid RIR databaseAPNIC 671 100% 66
161.121.128.0/20 Valid RIR databaseAPNIC 671 100% 66
2407:e500:40::/43 Valid RIR databaseAPNIC 635 100% 69
2407:e500:40::/47 Valid RIR databaseAPNIC 635 100% 69
2407:e500:50::/47 Valid RIR databaseAPNIC 635 100% 67

AS-SET

AS38910 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 6 are in fix.csv.

  • ROA: maxLength2
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength161.121.130.0/24ROA 161.121.128.0/19 AS38910 has maxLength 19; ROA 161.121.128.0/20 AS38910 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 161.121.130.0/24.135 of 673
Route object: none161.121.130.0/24No route object for it. A route object for 161.121.128.0/20 with origin AS38910 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38910 in the RIR database for the space.135 of 673
ROA: maxLength161.121.135.0/24ROA 161.121.128.0/19 AS38910 has maxLength 19; ROA 161.121.128.0/20 AS38910 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 161.121.135.0/24.135 of 673
Route object: none161.121.135.0/24No route object for it. A route object for 161.121.128.0/20 with origin AS38910 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38910 in the RIR database for the space.135 of 673

Route objects not announced

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

170.148.146.0/23RADBNo 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.