bgpreport

Network · data from 2026-11-12

AS1998 STATE-OF-MN - State of Minnesota

Registry name: STATE-OF-MN - State of Minnesota, US · not in PeeringDB

10IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
11No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS1998, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS1998, 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.

64.8.128.0/18 No ROA Other IRR onlyRADB 671 100% 70
151.111.0.0/16 No ROA Other IRR onlyRADB 671 100% 70
156.98.0.0/15 No ROA Other IRR onlyRADB 671 100% 70
192.112.135.0/24 No ROA Other IRR onlyRADB 671 100% 69
192.112.136.0/24 No ROA Other IRR onlyRADB 671 100% 69
192.112.137.0/24 No ROA Other IRR onlyRADB 671 100% 69
192.133.60.0/24 No ROA Other IRR onlyRADB 671 100% 70
192.156.191.0/24 No ROA Other IRR onlyRADB 671 100% 70
192.234.247.0/24 No ROA Other IRR onlyRADB 671 100% 70
207.171.64.0/18 No ROA Other IRR onlyRADB 671 100% 70
2607:f830::/32 No ROA Other IRR onlyRADB 634 100% 70

AS-SET

AS1998 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 22 are in fix.csv.

  • ROA: none11
  • Route object: RIR11
ChangePrefix or setDetailFull-table peers
ROA: none64.8.128.0/18No ROA covers it. Add a ROA for AS1998, maxLength 18.671 of 673
Route object: RIR64.8.128.0/18Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none151.111.0.0/16No ROA covers it. Add a ROA for AS1998, maxLength 16.671 of 673
Route object: RIR151.111.0.0/16Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none156.98.0.0/15No ROA covers it. Add a ROA for AS1998, maxLength 15.671 of 673
Route object: RIR156.98.0.0/15Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none192.112.135.0/24No ROA covers it. Add a ROA for AS1998, maxLength 24.671 of 673
Route object: RIR192.112.135.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none192.112.136.0/24No ROA covers it. Add a ROA for AS1998, maxLength 24.671 of 673
Route object: RIR192.112.136.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none192.112.137.0/24No ROA covers it. Add a ROA for AS1998, maxLength 24.671 of 673
Route object: RIR192.112.137.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none192.133.60.0/24No ROA covers it. Add a ROA for AS1998, maxLength 24.671 of 673
Route object: RIR192.133.60.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none192.156.191.0/24No ROA covers it. Add a ROA for AS1998, maxLength 24.671 of 673
Route object: RIR192.156.191.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none192.234.247.0/24No ROA covers it. Add a ROA for AS1998, maxLength 24.671 of 673
Route object: RIR192.234.247.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none207.171.64.0/18No ROA covers it. Add a ROA for AS1998, maxLength 18.671 of 673
Route object: RIR207.171.64.0/18Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2607:f830::/32No ROA covers it. Add a ROA for AS1998, maxLength 32.634 of 636
Route object: RIR2607:f830::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

Every route object with origin AS1998 is announced.

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.