Network · data from 2026-11-12
AS9419 NTU-AS-AP - Nanyang Technological University
Registry name: NTU-AS-AP - Nanyang Technological University, SG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9419, 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.
| 2407:9380:1::/48 | No ROA | None | 14 2%low visibility |
| 155.69.64.0/19 | Valid | Other IRR onlyRADB | 192 29% |
| 155.69.96.0/23 | Valid | Other IRR onlyRADB | 190 28% |
| 155.69.1.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 155.69.0.0/16 | Valid | RIR databaseAPNIC | 672 100% |
AS-SET
AS9419 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 4 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: RIR2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2407:9380:1::/48 | No ROA covers it. Add a ROA for AS9419, maxLength 48. |
| Route object: none | 2407:9380:1::/48 | No route object for it. Add a route object with origin AS9419 in the RIR database for the space. |
| Route object: RIR | 155.69.64.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 155.69.96.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS9419 is announced.
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.