Network · data from 2026-11-12
AS26333 UNONET - University of New Orleans
Registry name: UNONET - University of New Orleans, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26333, 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.30.0.0/17 | No ROA | Nonecovered by 137.30.0.0/16 | 673 100% |
| 137.30.128.0/18 | No ROA | Nonecovered by 137.30.0.0/16 | 673 100% |
| 137.30.192.0/19 | No ROA | Nonecovered by 137.30.0.0/16 | 673 100% |
| 137.30.224.0/20 | No ROA | Nonecovered by 137.30.0.0/16 | 673 100% |
| 137.30.240.0/21 | No ROA | Nonecovered by 137.30.0.0/16 | 673 100% |
| 76.165.128.0/19 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS26333 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.
- ROA: none6
- Route object: none5
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 137.30.0.0/17 | No ROA covers it. Add a ROA for AS26333, maxLength 17. |
| Route object: none | 137.30.0.0/17 | No route object for it. A route object for 137.30.0.0/16 with origin AS26333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26333 in the RIR database for the space. |
| ROA: none | 137.30.128.0/18 | No ROA covers it. Add a ROA for AS26333, maxLength 18. |
| Route object: none | 137.30.128.0/18 | No route object for it. A route object for 137.30.0.0/16 with origin AS26333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26333 in the RIR database for the space. |
| ROA: none | 137.30.192.0/19 | No ROA covers it. Add a ROA for AS26333, maxLength 19. |
| Route object: none | 137.30.192.0/19 | No route object for it. A route object for 137.30.0.0/16 with origin AS26333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26333 in the RIR database for the space. |
| ROA: none | 137.30.224.0/20 | No ROA covers it. Add a ROA for AS26333, maxLength 20. |
| Route object: none | 137.30.224.0/20 | No route object for it. A route object for 137.30.0.0/16 with origin AS26333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26333 in the RIR database for the space. |
| ROA: none | 137.30.240.0/21 | No ROA covers it. Add a ROA for AS26333, maxLength 21. |
| Route object: none | 137.30.240.0/21 | No route object for it. A route object for 137.30.0.0/16 with origin AS26333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26333 in the RIR database for the space. |
| ROA: none | 76.165.128.0/19 | No ROA covers it. Add a ROA for AS26333, maxLength 19. |
| Route object: RIR | 76.165.128.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS26333 whose prefix no peer sees AS26333 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 137.30.0.0/16 | RADB | No ROA |
| 192.31.223.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.