Network · data from 2026-11-12
AS393601 SMOA-STATEOFMISSOURI-01 - State of Missouri Office of Administration
Registry name: SMOA-STATEOFMISSOURI-01 - State of Missouri Office of Administration, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS393601, 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.
| 168.166.224.0/20 | No ROA | Other origin onlycovered by 168.166.0.0/16 | 670 100% |
| 168.166.0.0/16 | No ROA | Other IRR onlyRADB | 670 100% |
| 168.166.240.0/21 | No ROA | Other IRR onlyRADB | 670 100% |
| 2605:38c0::/32 | No ROA | Other IRR onlyRADB | 635 100% |
| 2620:108:a000::/44 | No ROA | Other IRR onlyRADB | 635 100% |
| 168.166.224.0/21 | No ROA | Other IRR onlyRADB | 4 1%low visibility |
| 168.166.232.0/22 | No ROA | Other IRR onlyRADB | 4 1%low visibility |
AS-SET
AS393601 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 15 are in fix.csv.
- ROA: none7
- Route object: none1
- Route object: RIR6
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 168.166.224.0/20 | No ROA covers it. Add a ROA for AS393601, maxLength 20. |
| Route object: none | 168.166.224.0/20 | Route objects for it name AS19905. A route object for 168.166.0.0/16 with origin AS393601 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393601 in the RIR database for the space. |
| ROA: none | 168.166.0.0/16 | No ROA covers it. Add a ROA for AS393601, maxLength 16. |
| Route object: RIR | 168.166.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 168.166.240.0/21 | No ROA covers it. Add a ROA for AS393601, maxLength 21. |
| Route object: RIR | 168.166.240.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2605:38c0::/32 | No ROA covers it. Add a ROA for AS393601, maxLength 32. |
| Route object: RIR | 2605:38c0::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2620:108:a000::/44 | No ROA covers it. Add a ROA for AS393601, maxLength 44. |
| Route object: RIR | 2620:108:a000::/44 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 168.166.224.0/21 | No ROA covers it. Add a ROA for AS393601, maxLength 21. |
| Route object: RIR | 168.166.224.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 168.166.232.0/22 | No ROA covers it. Add a ROA for AS393601, maxLength 22. |
| Route object: RIR | 168.166.232.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS393601 whose prefix no peer sees AS393601 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 168.166.74.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.