Network · data from 2026-11-12
AS46749 STANFORD-INTERNET-ACCESS - Stanford University
Registry name: STANFORD-INTERNET-ACCESS - Stanford University, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46749, 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.164.23.144/31 | No ROA | None | 1 0%low visibility |
| 2607:f380:1::118:9a41:7900/123 | No ROA | None | 1 0%low visibility |
| 68.65.160.0/20 | No ROA | Other IRR onlyRADB | 671 100% |
AS-SET
AS46749 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 7 are in fix.csv.
- ROA: none3
- Route object: none2
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 137.164.23.144/31 | No ROA covers it. Add a ROA for AS46749, maxLength 31. |
| Route object: none | 137.164.23.144/31 | No route object for it. Add a route object with origin AS46749 in the RIR database for the space. |
| ROA: none | 2607:f380:1::118:9a41:7900/123 | No ROA covers it. Add a ROA for AS46749, maxLength 123. |
| Route object: none | 2607:f380:1::118:9a41:7900/123 | No route object for it. Add a route object with origin AS46749 in the RIR database for the space. |
| ROA: none | 68.65.160.0/20 | No ROA covers it. Add a ROA for AS46749, maxLength 20. |
| Route object: RIR | 68.65.160.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS46749 whose prefix no peer sees AS46749 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 104.232.28.0/22 | RADB | 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.