Network · data from 2026-11-12
AS24090 Universiti Sains Malaysia
Registry name: UNISAINS-AS-AP - Universiti Sains Malaysia (USM), MY · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24090, 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.
| 2402:2200:a000::/40 | Invalid: maxLength | Nonecovered by 2402:2200:a000::/36 | 1 0%low visibility |
| 2402:2200:8000::/35 | No ROA | Other origin only | 635 100% |
| 202.170.54.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 202.170.53.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
| 202.170.52.0/23 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
| 202.170.48.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.170.56.0/21 | Valid | RIR databaseAPNIC | 672 100% |
| 202.170.56.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 202.170.58.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 202.170.60.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 202.170.48.0/23 | Valid | RIR databaseAPNIC | 671 100% |
| 202.170.49.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 202.170.50.0/23 | Valid | RIR databaseAPNIC | 671 100% |
| 202.170.50.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 202.170.51.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 202.170.62.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 202.170.56.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 202.170.57.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 202.170.58.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 202.170.59.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 202.170.60.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 202.170.61.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 202.170.62.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 202.170.63.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 2402:2200:6000::/35 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:2200:2000::/35 | Valid | RIR databaseAPNIC | 635 100% |
| 2402:2200:4000::/35 | Valid | RIR databaseAPNIC | 635 100% |
| 2402:2200:4000::/36 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2402:2200:5000::/36 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2402:2200:6000::/36 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2402:2200:7000::/36 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2402:2200:a000::/35 | Valid | RIR databaseAPNIC | 635 100% |
| 2402:2200:a000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2402:2200:c000::/35 | Valid | RIR databaseAPNIC | 635 100% |
| 2402:2200:c000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2402:2200:d000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2402:2200:2000::/36 | Valid | RIR databaseAPNIC | 634 100% |
| 2402:2200:3000::/36 | Valid | RIR databaseAPNIC | 634 100% |
| 2402:2200:3200::/40 | Valid | RIR databaseAPNIC | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS24090: AS-24090. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS24090 isn't in the set, or no route object for AS24090 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS24090 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-24090 | In no IRR database read today. | |||||
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.
- ROA: maxLength1
- ROA: none4
- Route object: none2
- Route object: RIR3
- AS-SET: not found1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 2402:2200:a000::/40 | ROA 2402:2200:a000::/35 AS24090 has maxLength 35; ROA 2402:2200:a000::/36 AS24090 has maxLength 36; the route is a /40. Raise the maxLength, or add a ROA for 2402:2200:a000::/40. |
| Route object: none | 2402:2200:a000::/40 | No route object for it. A route object for 2402:2200:a000::/36 with origin AS24090 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24090 in the RIR database for the space. |
| ROA: none | 2402:2200:8000::/35 | No ROA covers it. Add a ROA for AS24090, maxLength 35. |
| Route object: none | 2402:2200:8000::/35 | Route objects for it name AS4788. Add a route object with origin AS24090 in the RIR database for the space. |
| ROA: none | 202.170.54.0/23 | No ROA covers it. Add a ROA for AS24090, maxLength 23. |
| Route object: RIR | 202.170.54.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 202.170.53.0/24 | No ROA covers it. Add a ROA for AS24090, maxLength 24. |
| Route object: RIR | 202.170.53.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 202.170.52.0/23 | No ROA covers it. Add a ROA for AS24090, maxLength 23. |
| Route object: RIR | 202.170.52.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: not found | AS-24090 | PeeringDB names AS-24090; no IRR database read has it. |
Route objects not announced
Route objects with origin AS24090 whose prefix no peer sees AS24090 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.170.48.0/20 | RADB | No ROA |
| 202.170.52.0/22 | RADB | No ROA |
| 2402:2200:2a00::/40 | 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.