Network · data from 2026-11-12
AS38859 LINKLYTECH-AU - Linkly Technologies Pty Ltd
Registry name: LINKLYTECH-AU - Linkly Technologies Pty Ltd, AU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38859, 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.
| 101.97.56.32/27 | Invalid: origin | None | 1 0%low visibility |
| 103.91.167.0/27 | Invalid: origin | None | 1 0%low visibility |
| 202.166.187.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.195.127.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.83.209.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
AS-SET
AS38859 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 13 are in fix.csv.
- ROA: origin2
- ROA: none3
- Route object: none2
- Route object: RIR3
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 101.97.56.32/27 | ROAs covering it name AS15830, not AS38859. If AS38859 should announce it, add a ROA for AS38859. |
| Route object: none | 101.97.56.32/27 | No route object for it. Add a route object with origin AS38859 in the RIR database for the space. |
| ROA: origin | 103.91.167.0/27 | ROAs covering it name AS15830, not AS38859. If AS38859 should announce it, add a ROA for AS38859. |
| Route object: none | 103.91.167.0/27 | No route object for it. Add a route object with origin AS38859 in the RIR database for the space. |
| ROA: none | 202.166.187.0/24 | No ROA covers it. Add a ROA for AS38859, maxLength 24. |
| Route object: RIR | 202.166.187.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.195.127.0/24 | No ROA covers it. Add a ROA for AS38859, maxLength 24. |
| Route object: RIR | 203.195.127.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 103.83.209.0/24 | No ROA covers it. Add a ROA for AS38859, maxLength 24. |
| Route object: RIR | 103.83.209.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38859 whose prefix no peer sees AS38859 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.83.208.0/23 | NTTCOM | No ROA |
| 103.83.208.0/24 | NTTCOM | No ROA |
| 103.219.241.0/24 | NTTCOM | 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.