Network · data from 2026-11-12
AS14425 MENDO-COMMUNITY-NET - Mendocino Community Network
Registry name: MENDO-COMMUNITY-NET - Mendocino Community Network, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS14425, 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.
| 216.150.250.0/24 | No ROA | Nonecovered by 216.150.240.0/20 | 671 100% |
| 216.150.251.0/24 | No ROA | Nonecovered by 216.150.240.0/20 | 671 100% |
AS-SET
AS14425 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 10 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 216.150.250.0/24 | No ROA covers it. Add a ROA for AS14425, maxLength 24. |
| Route object: none | 216.150.250.0/24 | No route object for it. A route object for 216.150.240.0/20 with origin AS14425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14425 in the RIR database for the space. |
| ROA: none | 216.150.251.0/24 | No ROA covers it. Add a ROA for AS14425, maxLength 24. |
| Route object: none | 216.150.251.0/24 | No route object for it. A route object for 216.150.240.0/20 with origin AS14425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14425 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS14425 whose prefix no peer sees AS14425 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 63.193.12.0/22 | RADB | No ROA |
| 63.194.153.0/24 | RADB | No ROA |
| 207.213.215.0/24 | RADB | No ROA |
| 207.213.216.0/24 | RADB | No ROA |
| 207.213.217.0/24 | RADB | No ROA |
| 216.150.240.0/20 | 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.