Network · data from 2026-11-12
AS46788 IMSD-AS1 - Milwaukee County Government
Registry name: IMSD-AS1 - Milwaukee County Government, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46788, 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.
| 204.194.253.0/24 | No ROA | Nonecovered by 204.194.252.0/23 | 673 100% |
| 204.194.248.0/22 | No ROA | Other IRR onlyRADB | 668 99% |
AS-SET
AS46788 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 11 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: RIR1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 204.194.253.0/24 | No ROA covers it. Add a ROA for AS46788, maxLength 24. |
| Route object: none | 204.194.253.0/24 | No route object for it. A route object for 204.194.252.0/23 with origin AS46788 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46788 in the RIR database for the space. |
| ROA: none | 204.194.248.0/22 | No ROA covers it. Add a ROA for AS46788, maxLength 22. |
| Route object: RIR | 204.194.248.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS46788 whose prefix no peer sees AS46788 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 204.194.248.0/21 | RADB | No ROA |
| 204.194.252.0/22 | RADB | No ROA |
| 204.194.252.0/23 | RADB | No ROA |
| 204.194.252.0/24 | RADB | No ROA |
| 204.194.254.0/24 | RADB | No ROA |
| 204.194.255.0/24 | RADB | No ROA |
| 2620:120:b000::/40 | 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.