Network · data from 2026-11-12
AS38481 JPMORGAN-TRANSIT-AS-SG-AP - JPMORGAN Singapore
Registry name: JPMORGAN-TRANSIT-AS-SG-AP - JPMORGAN Singapore, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38481, 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.
| 2407:e500:20::/43 | No ROA | Other IRR onlyRADB | 636 100% |
| 161.121.224.0/19 | Valid | RIR databaseARIN, RADB | 672 100% |
| 170.148.224.0/20 | Valid | RIR databaseARIN, RADB | 672 100% |
| 161.121.224.0/20 | Valid | RIR databaseARIN, RADB | 671 100% |
| 161.121.240.0/20 | Valid | RIR databaseARIN | 671 100% |
| 170.148.224.0/21 | Valid | RIR databaseARIN, RADB | 671 100% |
| 170.148.232.0/21 | Valid | RIR databaseARIN | 671 100% |
| 2407:e500:20::/47 | Valid | RIR databaseAPNIC | 636 100% |
| 2407:e500:30::/47 | Valid | RIR databaseAPNIC | 635 100% |
AS-SET
AS38481 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 5 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2407:e500:20::/43 | No ROA covers it. Add a ROA for AS38481, maxLength 43. |
| Route object: RIR | 2407:e500:20::/43 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38481 whose prefix no peer sees AS38481 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 204.86.14.0/23 | ARIN | Invalid: origin |
| 2407:e500:8::/47 | APNIC | Valid |
| 2407:e500:a::/47 | APNIC | Valid |
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.