Network · data from 2026-11-12
AS24253 J-Stream
Registry name: J-Stream - J-Stream Inc., JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24253, 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.
| 2401:dc40::/32 | No ROA | Other IRR onlyJPIRR | 633 100% |
| 202.79.240.0/21 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 103.157.156.0/24 | Valid | Other IRR onlyJPIRR | 671 100% |
AS-SET
AS24253'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 6 are in fix.csv.
- ROA: none1
- Route object: RIR3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2401:dc40::/32 | No ROA covers it. Add a ROA for AS24253, maxLength 32. |
| Route object: RIR | 2401:dc40::/32 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 202.79.240.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.157.156.0/24 | Route object only in JPIRR. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24253 whose prefix no peer sees AS24253 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2401:d0a0:8000::/34 | JPIRR | Invalid: origin |
| 2401:d0a0:c000::/34 | JPIRR | Invalid: 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.