Network · data from 2026-11-12
AS26 Cornell
Registry name: CORNELL - Cornell University, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26, 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.
| 128.84.0.0/16 | No ROA | Other IRR onlyRADB | 671 100% |
| 128.253.0.0/16 | No ROA | Other IRR onlyRADB | 671 100% |
| 132.236.0.0/16 | No ROA | Other IRR onlyRADB | 671 100% |
| 192.35.82.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 192.122.235.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 192.122.236.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 2620:110:d000::/44 | Valid | RIR databaseARIN, RADB | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS26: RADB::AS26:AS-ALL. 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 (AS26 isn't in the set, or no route object for AS26 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 | AS26 in it | Not covered |
|---|---|---|---|---|---|
| RADB::AS26:AS-ALL | RADB | 1 | 1 | Yes | 0 |
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 12 are in fix.csv.
- ROA: none6
- Route object: RIR6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 128.84.0.0/16 | No ROA covers it. Add a ROA for AS26, maxLength 16. |
| Route object: RIR | 128.84.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 128.253.0.0/16 | No ROA covers it. Add a ROA for AS26, maxLength 16. |
| Route object: RIR | 128.253.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 132.236.0.0/16 | No ROA covers it. Add a ROA for AS26, maxLength 16. |
| Route object: RIR | 132.236.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.35.82.0/24 | No ROA covers it. Add a ROA for AS26, maxLength 24. |
| Route object: RIR | 192.35.82.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.122.235.0/24 | No ROA covers it. Add a ROA for AS26, maxLength 24. |
| Route object: RIR | 192.122.235.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.122.236.0/24 | No ROA covers it. Add a ROA for AS26, maxLength 24. |
| Route object: RIR | 192.122.236.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS26 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.