Network · data from 2026-11-12
AS396001 TACO-396001 - City of Tacoma
Registry name: TACO-396001 - City of Tacoma, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS396001, 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.
| 131.191.200.0/23 | No ROA | Nonecovered by 131.191.128.0/17 | 673 100% |
| 131.191.250.0/24 | No ROA | Nonecovered by 131.191.128.0/17 | 672 100% |
| 131.191.128.0/24 | No ROA | Nonecovered by 131.191.128.0/17 | 671 100% |
| 131.191.210.0/24 | No ROA | Nonecovered by 131.191.128.0/17 | 668 99% |
| 131.191.129.0/24 | No ROA | Nonecovered by 131.191.128.0/17 | 667 99% |
| 131.191.128.0/17 | No ROA | Other IRR onlyRADB | 673 100% |
| 131.191.240.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 192.103.239.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 131.191.251.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 131.191.254.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 192.103.238.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 192.103.238.0/24 | No ROA | Other IRR onlyRADB | 667 99% |
AS-SET
AS396001 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 25 are in fix.csv.
- ROA: none12
- Route object: none5
- Route object: RIR7
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 131.191.200.0/23 | No ROA covers it. Add a ROA for AS396001, maxLength 23. |
| Route object: none | 131.191.200.0/23 | No route object for it. A route object for 131.191.128.0/17 with origin AS396001 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396001 in the RIR database for the space. |
| ROA: none | 131.191.250.0/24 | No ROA covers it. Add a ROA for AS396001, maxLength 24. |
| Route object: none | 131.191.250.0/24 | No route object for it. A route object for 131.191.128.0/17 with origin AS396001 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396001 in the RIR database for the space. |
| ROA: none | 131.191.128.0/24 | No ROA covers it. Add a ROA for AS396001, maxLength 24. |
| Route object: none | 131.191.128.0/24 | No route object for it. A route object for 131.191.128.0/17 with origin AS396001 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396001 in the RIR database for the space. |
| ROA: none | 131.191.210.0/24 | No ROA covers it. Add a ROA for AS396001, maxLength 24. |
| Route object: none | 131.191.210.0/24 | No route object for it. A route object for 131.191.128.0/17 with origin AS396001 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396001 in the RIR database for the space. |
| ROA: none | 131.191.129.0/24 | No ROA covers it. Add a ROA for AS396001, maxLength 24. |
| Route object: none | 131.191.129.0/24 | No route object for it. A route object for 131.191.128.0/17 with origin AS396001 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396001 in the RIR database for the space. |
| ROA: none | 131.191.128.0/17 | No ROA covers it. Add a ROA for AS396001, maxLength 17. |
| Route object: RIR | 131.191.128.0/17 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 131.191.240.0/24 | No ROA covers it. Add a ROA for AS396001, maxLength 24. |
| Route object: RIR | 131.191.240.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.103.239.0/24 | No ROA covers it. Add a ROA for AS396001, maxLength 24. |
| Route object: RIR | 192.103.239.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 131.191.251.0/24 | No ROA covers it. Add a ROA for AS396001, maxLength 24. |
| Route object: RIR | 131.191.251.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 131.191.254.0/24 | No ROA covers it. Add a ROA for AS396001, maxLength 24. |
| Route object: RIR | 131.191.254.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.103.238.0/23 | No ROA covers it. Add a ROA for AS396001, maxLength 23. |
| Route object: RIR | 192.103.238.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.103.238.0/24 | No ROA covers it. Add a ROA for AS396001, maxLength 24. |
| Route object: RIR | 192.103.238.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS396001 whose prefix no peer sees AS396001 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 131.191.230.0/23 | 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.