Network · data from 2026-11-12
AS138449 SYUNET-AS-AP - SIANG YU SCIENCE AND TECHNOLOGY LIMITED
Registry name: SYUNET-AS-AP - SIANG YU SCIENCE AND TECHNOLOGY LIMITED, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS138449, 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.
| 122.113.50.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 139.183.100.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 42.0.200.0/24 | No ROA | Other IRR onlyRADB | 665 99% |
AS-SET
AS138449 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 10 are in fix.csv.
- ROA: none3
- Route object: RIR3
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 122.113.50.0/24 | No ROA covers it. Add a ROA for AS138449, maxLength 24. |
| Route object: RIR | 122.113.50.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 139.183.100.0/24 | No ROA covers it. Add a ROA for AS138449, maxLength 24. |
| Route object: RIR | 139.183.100.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 42.0.200.0/24 | No ROA covers it. Add a ROA for AS138449, maxLength 24. |
| Route object: RIR | 42.0.200.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS138449 whose prefix no peer sees AS138449 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 27.103.150.0/24 | NTTCOM, RADB | No ROA |
| 111.66.101.0/24 | NTTCOM, RADB | No ROA |
| 116.196.202.0/24 | NTTCOM, RADB | No ROA |
| 120.30.150.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.