Network · data from 2026-11-12
AS10309 MARIN-MIDAS - County of Marin
Registry name: MARIN-MIDAS - County of Marin, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS10309, 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.
| 199.88.116.0/23 | No ROA | None | 670 100% |
| 199.88.118.0/24 | No ROA | None | 667 99% |
| 199.88.113.0/24 | No ROA | Other origin only | 416 62% |
| 199.88.64.0/21 | No ROA | Other IRR onlyRADB | 672 100% |
| 199.88.80.0/21 | No ROA | Other IRR onlyRADB | 672 100% |
| 199.88.120.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 199.88.72.0/22 | No ROA | Other IRR onlyRADB | 670 100% |
| 199.88.88.0/22 | No ROA | Other IRR onlyRADB | 670 100% |
| 199.88.76.0/23 | No ROA | Other IRR onlyRADB | 313 47% |
| 199.88.79.0/24 | No ROA | Other IRR onlyRADB | 313 47% |
| 199.88.114.0/23 | No ROA | Other IRR onlyRADB | 313 47% |
| 107.0.46.0/23 | Valid | Other IRR onlyRADB | 663 99% |
AS-SET
AS10309 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 23 are in fix.csv.
- ROA: none11
- Route object: none3
- Route object: RIR9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 199.88.116.0/23 | No ROA covers it. Add a ROA for AS10309, maxLength 23. |
| Route object: none | 199.88.116.0/23 | No route object for it. Add a route object with origin AS10309 in the RIR database for the space. |
| ROA: none | 199.88.118.0/24 | No ROA covers it. Add a ROA for AS10309, maxLength 24. |
| Route object: none | 199.88.118.0/24 | No route object for it. Add a route object with origin AS10309 in the RIR database for the space. |
| ROA: none | 199.88.113.0/24 | No ROA covers it. Add a ROA for AS10309, maxLength 24. |
| Route object: none | 199.88.113.0/24 | Route objects for it name AS31802. Add a route object with origin AS10309 in the RIR database for the space. |
| ROA: none | 199.88.64.0/21 | No ROA covers it. Add a ROA for AS10309, maxLength 21. |
| Route object: RIR | 199.88.64.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.88.80.0/21 | No ROA covers it. Add a ROA for AS10309, maxLength 21. |
| Route object: RIR | 199.88.80.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.88.120.0/23 | No ROA covers it. Add a ROA for AS10309, maxLength 23. |
| Route object: RIR | 199.88.120.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.88.72.0/22 | No ROA covers it. Add a ROA for AS10309, maxLength 22. |
| Route object: RIR | 199.88.72.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.88.88.0/22 | No ROA covers it. Add a ROA for AS10309, maxLength 22. |
| Route object: RIR | 199.88.88.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.88.76.0/23 | No ROA covers it. Add a ROA for AS10309, maxLength 23. |
| Route object: RIR | 199.88.76.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.88.79.0/24 | No ROA covers it. Add a ROA for AS10309, maxLength 24. |
| Route object: RIR | 199.88.79.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.88.114.0/23 | No ROA covers it. Add a ROA for AS10309, maxLength 23. |
| Route object: RIR | 199.88.114.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 107.0.46.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS10309 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.