Network · data from 2026-11-12
AS398191 Tri-Co Connections
Registry name: TRI-CO-CONNECTIONS - Tri-Co Connections, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS398191, 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.
| 38.252.240.0/20 | No ROA | Other IRR onlyRADB | 673 100% |
| 216.225.36.0/22 | Valid | Nonecovered by 216.225.32.0/19 | 671 100% |
| 64.45.128.0/24 | Valid | Nonecovered by 64.45.128.0/20 | 667 99% |
| 216.225.33.0/24 | Valid | Nonecovered by 216.225.32.0/19 | 667 99% |
| 216.225.34.0/24 | Valid | Nonecovered by 216.225.32.0/19 | 667 99% |
| 216.225.51.0/24 | Valid | Nonecovered by 216.225.32.0/19 | 667 99% |
| 216.225.52.0/24 | Valid | Nonecovered by 216.225.32.0/19 | 667 99% |
| 64.45.128.0/20 | Valid | RIR databaseARIN | 673 100% |
| 64.45.144.0/21 | Valid | RIR databaseARIN | 673 100% |
| 216.225.32.0/19 | Valid | RIR databaseARIN | 673 100% |
| 216.225.56.0/22 | Valid | RIR databaseARIN | 673 100% |
| 216.225.36.0/24 | Valid | RIR databaseARIN | 668 99% |
| 216.225.37.0/24 | Valid | RIR databaseARIN | 668 99% |
| 216.225.38.0/24 | Valid | RIR databaseARIN | 668 99% |
| 216.225.39.0/24 | Valid | RIR databaseARIN | 668 99% |
| 216.225.32.0/24 | Valid | RIR databaseARIN | 667 99% |
AS-SET
AS398191's PeeringDB record names no 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: none1
- Route object: none6
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.252.240.0/20 | No ROA covers it. Add a ROA for AS398191, maxLength 20. |
| Route object: RIR | 38.252.240.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 216.225.36.0/22 | No route object for it. A route object for 216.225.32.0/19 with origin AS398191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398191 in the RIR database for the space. |
| Route object: none | 64.45.128.0/24 | No route object for it. A route object for 64.45.128.0/20 with origin AS398191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398191 in the RIR database for the space. |
| Route object: none | 216.225.33.0/24 | No route object for it. A route object for 216.225.32.0/19 with origin AS398191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398191 in the RIR database for the space. |
| Route object: none | 216.225.34.0/24 | No route object for it. A route object for 216.225.32.0/19 with origin AS398191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398191 in the RIR database for the space. |
| Route object: none | 216.225.51.0/24 | No route object for it. A route object for 216.225.32.0/19 with origin AS398191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398191 in the RIR database for the space. |
| Route object: none | 216.225.52.0/24 | No route object for it. A route object for 216.225.32.0/19 with origin AS398191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398191 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS398191 whose prefix no peer sees AS398191 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 216.225.44.0/22 | ARIN | Valid |
| 2607:c7c0::/32 | ARIN | 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.