Network · data from 2026-11-12
AS6106 UCR-EDU - University of California, Riverside
Registry name: UCR-EDU - University of California, Riverside, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS6106, 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.
| 138.23.104.0/22 | No ROA | Nonecovered by 138.23.0.0/16 | 19 3%low visibility |
| 2607:f290:10::/48 | No ROA | Nonecovered by 2607:f290::/32 | 17 3%low visibility |
| 137.164.23.16/31 | No ROA | None | 1 0%low visibility |
| 137.164.24.208/31 | No ROA | None | 1 0%low visibility |
| 137.164.24.210/31 | No ROA | None | 1 0%low visibility |
| 2607:f380:1::118:9a41:8d00/123 | No ROA | None | 1 0%low visibility |
| 2607:f380:1::118:9a41:8d20/123 | No ROA | None | 1 0%low visibility |
| 192.31.146.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 138.23.0.0/16 | No ROA | Other IRR onlyRADB | 669 99% |
| 169.235.0.0/16 | No ROA | Other IRR onlyRADB | 669 99% |
| 2607:f290::/32 | No ROA | Other IRR onlyRADB | 633 100% |
AS-SET
AS6106 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 22 are in fix.csv.
- ROA: none11
- Route object: none7
- Route object: RIR4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 138.23.104.0/22 | No ROA covers it. Add a ROA for AS6106, maxLength 22. |
| Route object: none | 138.23.104.0/22 | No route object for it. A route object for 138.23.0.0/16 with origin AS6106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6106 in the RIR database for the space. |
| ROA: none | 2607:f290:10::/48 | No ROA covers it. Add a ROA for AS6106, maxLength 48. |
| Route object: none | 2607:f290:10::/48 | No route object for it. A route object for 2607:f290::/32 with origin AS6106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6106 in the RIR database for the space. |
| ROA: none | 137.164.23.16/31 | No ROA covers it. Add a ROA for AS6106, maxLength 31. |
| Route object: none | 137.164.23.16/31 | No route object for it. Add a route object with origin AS6106 in the RIR database for the space. |
| ROA: none | 137.164.24.208/31 | No ROA covers it. Add a ROA for AS6106, maxLength 31. |
| Route object: none | 137.164.24.208/31 | No route object for it. Add a route object with origin AS6106 in the RIR database for the space. |
| ROA: none | 137.164.24.210/31 | No ROA covers it. Add a ROA for AS6106, maxLength 31. |
| Route object: none | 137.164.24.210/31 | No route object for it. Add a route object with origin AS6106 in the RIR database for the space. |
| ROA: none | 2607:f380:1::118:9a41:8d00/123 | No ROA covers it. Add a ROA for AS6106, maxLength 123. |
| Route object: none | 2607:f380:1::118:9a41:8d00/123 | No route object for it. Add a route object with origin AS6106 in the RIR database for the space. |
| ROA: none | 2607:f380:1::118:9a41:8d20/123 | No ROA covers it. Add a ROA for AS6106, maxLength 123. |
| Route object: none | 2607:f380:1::118:9a41:8d20/123 | No route object for it. Add a route object with origin AS6106 in the RIR database for the space. |
| ROA: none | 192.31.146.0/24 | No ROA covers it. Add a ROA for AS6106, maxLength 24. |
| Route object: RIR | 192.31.146.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 138.23.0.0/16 | No ROA covers it. Add a ROA for AS6106, maxLength 16. |
| Route object: RIR | 138.23.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 169.235.0.0/16 | No ROA covers it. Add a ROA for AS6106, maxLength 16. |
| Route object: RIR | 169.235.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2607:f290::/32 | No ROA covers it. Add a ROA for AS6106, maxLength 32. |
| Route object: RIR | 2607:f290::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS6106 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.