Network · data from 2026-11-12
AS4783 SYSNET-AS1 - SYSTEX CORPORATION
Registry name: SYSNET-AS1 - SYSTEX CORPORATION, TW · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS4783, 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.
| 210.63.0.0/19 | Valid | Nonecovered by 210.63.0.0/18 | 672 100% |
| 210.67.0.0/20 | Valid | Nonecovered by 210.67.0.0/18 | 672 100% |
| 210.67.16.0/20 | Valid | Nonecovered by 210.67.0.0/18 | 672 100% |
| 210.67.32.0/19 | Valid | Nonecovered by 210.67.0.0/18 | 672 100% |
| 202.39.96.0/20 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 210.63.32.0/19 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 210.67.112.0/20 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
AS-SET
AS4783 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 14 are in fix.csv.
- Route object: none4
- Route object: RIR3
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 210.63.0.0/19 | No route object for it. A route object for 210.63.0.0/18 with origin AS4783 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4783 in the RIR database for the space. |
| Route object: none | 210.67.0.0/20 | No route object for it. A route object for 210.67.0.0/18 with origin AS4783 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4783 in the RIR database for the space. |
| Route object: none | 210.67.16.0/20 | No route object for it. A route object for 210.67.0.0/18 with origin AS4783 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4783 in the RIR database for the space. |
| Route object: none | 210.67.32.0/19 | No route object for it. A route object for 210.67.0.0/18 with origin AS4783 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4783 in the RIR database for the space. |
| Route object: RIR | 202.39.96.0/20 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.63.32.0/19 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 210.67.112.0/20 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS4783 whose prefix no peer sees AS4783 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.39.96.0/21 | NTTCOM | Valid |
| 202.39.104.0/21 | NTTCOM | Valid |
| 210.63.0.0/18 | NTTCOM, RADB | No ROA |
| 210.63.0.0/21 | NTTCOM | Valid |
| 210.67.0.0/18 | NTTCOM, RADB | No ROA |
| 210.67.128.0/20 | NTTCOM, RADB | No ROA |
| 2405:a00::/32 | RADB | 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.