bgpreport

Network · data from 2026-11-12

AS217 UMN System Network

Registry name: UMN-SYSTEM - University of Minnesota, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS217, 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.
131.212.0.0/16 No ROA RIR databaseARIN, RADB 671 100% 69
134.84.0.0/16 No ROA RIR databaseARIN, RADB 671 100% 69
146.57.0.0/16 No ROA RIR databaseARIN, RADB 671 100% 69
160.94.0.0/16 No ROA RIR databaseARIN, RADB 671 100% 69
128.101.0.0/16 No ROA RIR databaseARIN, RADB 668 99% 69
2001:470:22::/48 Valid RIR databaseARIN, RADB 634 100% 70

AS-SET

AS217'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 6 are in fix.csv.

  • ROA: none5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none131.212.0.0/16No ROA covers it. Add a ROA for AS217, maxLength 16.671 of 673
ROA: none134.84.0.0/16No ROA covers it. Add a ROA for AS217, maxLength 16.671 of 673
ROA: none146.57.0.0/16No ROA covers it. Add a ROA for AS217, maxLength 16.671 of 673
ROA: none160.94.0.0/16No ROA covers it. Add a ROA for AS217, maxLength 16.671 of 673
ROA: none128.101.0.0/16No ROA covers it. Add a ROA for AS217, maxLength 16.668 of 673

Route objects not announced

Route objects with origin AS217 whose prefix no peer sees AS217 announce. Many are kept on purpose (backup routes, space announced only in some places).

64.62.149.0/24ARINValid

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.