Network · data from 2026-11-12
AS394305 JLINK-ASN - Jlink, Inc
Registry name: JLINK-ASN - Jlink, Inc, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS394305, 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.
| 206.126.248.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 172.110.163.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
| 216.75.133.0/24 | Valid | RIR databaseARIN, RADB | 669 99% |
AS-SET
AS394305 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 7 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 206.126.248.0/23 | No ROA covers it. Add a ROA for AS394305, maxLength 23. |
| Route object: RIR | 206.126.248.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 172.110.163.0/24 | No ROA covers it. Add a ROA for AS394305, maxLength 24. |
| Route object: RIR | 172.110.163.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS394305 whose prefix no peer sees AS394305 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.123.163.0/24 | RADB | No ROA |
| 130.12.127.0/24 | RADB | No ROA |
| 134.195.253.0/24 | RADB | No 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.