Network · data from 2026-11-12
AS7472 NUS-AS-AP - NUS Information Technology
Registry name: NUS-AS-AP - NUS Information Technology, SG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS7472, 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.
| 137.132.5.0/24 | No ROA | Nonecovered by 137.132.0.0/17 | 670 100% |
| 137.132.10.0/24 | No ROA | Nonecovered by 137.132.0.0/17 | 670 100% |
| 137.132.21.0/24 | No ROA | Nonecovered by 137.132.0.0/17 | 670 100% |
| 137.132.174.0/24 | No ROA | Nonecovered by 137.132.128.0/17 | 670 100% |
| 137.132.250.0/24 | No ROA | Nonecovered by 137.132.128.0/17 | 670 100% |
| 137.132.0.0/16 | No ROA | Other IRR onlyRADB | 672 100% |
| 137.132.0.0/17 | No ROA | Other IRR onlyRADB | 4 1%low visibility |
| 137.132.128.0/17 | No ROA | Other IRR onlyRADB | 4 1%low visibility |
AS-SET
AS7472 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 18 are in fix.csv.
- ROA: none8
- Route object: none5
- Route object: RIR3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 137.132.5.0/24 | No ROA covers it. Add a ROA for AS7472, maxLength 24. |
| Route object: none | 137.132.5.0/24 | No route object for it. A route object for 137.132.0.0/17 with origin AS7472 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7472 in the RIR database for the space. |
| ROA: none | 137.132.10.0/24 | No ROA covers it. Add a ROA for AS7472, maxLength 24. |
| Route object: none | 137.132.10.0/24 | No route object for it. A route object for 137.132.0.0/17 with origin AS7472 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7472 in the RIR database for the space. |
| ROA: none | 137.132.21.0/24 | No ROA covers it. Add a ROA for AS7472, maxLength 24. |
| Route object: none | 137.132.21.0/24 | No route object for it. A route object for 137.132.0.0/17 with origin AS7472 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7472 in the RIR database for the space. |
| ROA: none | 137.132.174.0/24 | No ROA covers it. Add a ROA for AS7472, maxLength 24. |
| Route object: none | 137.132.174.0/24 | No route object for it. A route object for 137.132.128.0/17 with origin AS7472 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7472 in the RIR database for the space. |
| ROA: none | 137.132.250.0/24 | No ROA covers it. Add a ROA for AS7472, maxLength 24. |
| Route object: none | 137.132.250.0/24 | No route object for it. A route object for 137.132.128.0/17 with origin AS7472 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7472 in the RIR database for the space. |
| ROA: none | 137.132.0.0/16 | No ROA covers it. Add a ROA for AS7472, maxLength 16. |
| Route object: RIR | 137.132.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 137.132.0.0/17 | No ROA covers it. Add a ROA for AS7472, maxLength 17. |
| Route object: RIR | 137.132.0.0/17 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 137.132.128.0/17 | No ROA covers it. Add a ROA for AS7472, maxLength 17. |
| Route object: RIR | 137.132.128.0/17 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS7472 whose prefix no peer sees AS7472 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 137.132.0.0/24 | RADB | No ROA |
| 202.0.149.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.