Network · data from 2026-11-12
AS54885 STATE-OF-IDAHO-SECONDARY-ASN - State of Idaho
Registry name: STATE-OF-IDAHO-SECONDARY-ASN - State of Idaho, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS54885, 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.
| 164.165.254.0/23 | Valid | Nonecovered by 164.165.0.0/16 | 671 100% |
| 164.165.0.0/16 | Valid | RIR databaseARIN, RADB | 672 100% |
| 164.165.0.0/17 | Valid | RIR databaseARIN | 671 100% |
| 164.165.128.0/18 | Valid | RIR databaseARIN | 671 100% |
| 164.165.192.0/19 | Valid | RIR databaseARIN | 671 100% |
| 164.165.224.0/20 | Valid | RIR databaseARIN | 671 100% |
| 164.165.240.0/21 | Valid | RIR databaseARIN | 671 100% |
| 164.165.248.0/22 | Valid | RIR databaseARIN | 671 100% |
| 192.102.16.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 192.207.45.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 204.144.104.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
AS-SET
AS54885 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 2 are in fix.csv.
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 164.165.254.0/23 | No route object for it. A route object for 164.165.0.0/16 with origin AS54885 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54885 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS54885 whose prefix no peer sees AS54885 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2601:3000::/28 | 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.