Network · data from 2026-11-12
AS133014 UTM-AS-AP - Universiti Teknologi Malaysia
Registry name: UTM-AS-AP - Universiti Teknologi Malaysia, MY · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS133014, 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.
| 161.139.0.0/17 | No ROA | Other IRR onlyRADB | 672 100% |
| 161.139.224.0/19 | No ROA | Other IRR onlyRADB | 672 100% |
| 161.139.128.0/21 | Valid | Other IRR onlyRADB | 669 99% |
| 161.139.136.0/21 | Valid | Other IRR onlyRADB | 669 99% |
| 161.139.208.0/21 | Valid | Other IRR onlyRADB | 669 99% |
| 161.139.216.0/21 | Valid | Other IRR onlyRADB | 669 99% |
| 161.139.128.0/20 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 161.139.208.0/20 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 161.139.0.0/20 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 161.139.16.0/20 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 161.139.32.0/20 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 161.139.48.0/20 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 161.139.64.0/20 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 161.139.80.0/20 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 161.139.96.0/20 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 161.139.112.0/20 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 161.139.152.0/22 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 161.139.156.0/22 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 161.139.168.0/24 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 161.139.224.0/20 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 161.139.240.0/20 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 2001:df0:41f::/48 | Valid | RIR databaseAPNIC, RADB | 634 100% |
AS-SET
AS133014 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 70 are in fix.csv.
- ROA: none2
- Route object: RIR6
- Route object: not announced62
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 161.139.0.0/17 | No ROA covers it. Add a ROA for AS133014, maxLength 17. |
| Route object: RIR | 161.139.0.0/17 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 161.139.224.0/19 | No ROA covers it. Add a ROA for AS133014, maxLength 19. |
| Route object: RIR | 161.139.224.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 161.139.128.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 161.139.136.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 161.139.208.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 161.139.216.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS133014 whose prefix no peer sees AS133014 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 161.139.0.0/16 | APNIC | No ROA |
| 161.139.144.0/20 | APNIC | Valid |
| 161.139.144.0/21 | APNIC | Valid |
| 161.139.144.0/22 | APNIC | Valid |
| 161.139.144.0/23 | APNIC | Valid |
| 161.139.144.0/24 | APNIC | Valid |
| 161.139.145.0/24 | APNIC | Valid |
| 161.139.146.0/23 | APNIC | Valid |
| 161.139.146.0/24 | APNIC | Valid |
| 161.139.147.0/24 | APNIC | Valid |
| 161.139.148.0/22 | APNIC | Valid |
| 161.139.148.0/23 | APNIC | Valid |
| 161.139.148.0/24 | APNIC | Valid |
| 161.139.149.0/24 | APNIC | Valid |
| 161.139.150.0/23 | APNIC | Valid |
| 161.139.150.0/24 | APNIC | Valid |
| 161.139.151.0/24 | APNIC | Valid |
| 161.139.152.0/21 | APNIC | Valid |
| 161.139.152.0/23 | APNIC | Valid |
| 161.139.152.0/24 | APNIC | Valid |
| 161.139.153.0/24 | APNIC | Valid |
| 161.139.154.0/23 | APNIC | Valid |
| 161.139.154.0/24 | APNIC | Valid |
| 161.139.155.0/24 | APNIC | Valid |
| 161.139.156.0/23 | APNIC | Valid |
| 161.139.156.0/24 | APNIC | Valid |
| 161.139.157.0/24 | APNIC | Valid |
| 161.139.158.0/23 | APNIC | Valid |
| 161.139.158.0/24 | APNIC | Valid |
| 161.139.159.0/24 | APNIC | Valid |
| 161.139.160.0/20 | APNIC | Valid |
| 161.139.160.0/21 | APNIC | Valid |
| 161.139.160.0/22 | APNIC | Valid |
| 161.139.160.0/23 | APNIC | Valid |
| 161.139.160.0/24 | APNIC | Valid |
| 161.139.161.0/24 | APNIC | Valid |
| 161.139.162.0/23 | APNIC | Valid |
| 161.139.162.0/24 | APNIC | Valid |
| 161.139.163.0/24 | APNIC | Valid |
| 161.139.164.0/22 | APNIC | Valid |
| 161.139.164.0/23 | APNIC | Valid |
| 161.139.164.0/24 | APNIC | Valid |
| 161.139.165.0/24 | APNIC | Valid |
| 161.139.166.0/23 | APNIC | Valid |
| 161.139.166.0/24 | APNIC | Valid |
| 161.139.167.0/24 | APNIC | Valid |
| 161.139.168.0/21 | APNIC | Valid |
| 161.139.168.0/22 | APNIC | Valid |
| 161.139.168.0/23 | APNIC | Valid |
| 161.139.169.0/24 | APNIC | Valid |
| 161.139.170.0/23 | APNIC | Valid |
| 161.139.170.0/24 | APNIC | Valid |
| 161.139.171.0/24 | APNIC | Valid |
| 161.139.172.0/22 | APNIC | Valid |
| 161.139.172.0/23 | APNIC | Valid |
| 161.139.172.0/24 | APNIC | Valid |
| 161.139.173.0/24 | APNIC | Valid |
| 161.139.174.0/23 | APNIC | Valid |
| 161.139.174.0/24 | APNIC | Valid |
| 161.139.175.0/24 | APNIC | Valid |
| 161.139.176.0/20 | APNIC | Valid |
| 161.139.192.0/20 | APNIC | 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.