bgpreport

Network · data from 2026-11-12

AS11500 MSOE-INTERNET - Milwaukee School of Engineering

Registry name: MSOE-INTERNET - Milwaukee School of Engineering, US · not in PeeringDB

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

Announced routes

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

155.92.0.0/18 No ROA Nonecovered by 155.92.0.0/16 670 100% 69
155.92.0.0/24 No ROA Nonecovered by 155.92.0.0/16 670 100% 69
155.92.11.0/24 No ROA Nonecovered by 155.92.0.0/16 670 100% 70
155.92.64.0/19 No ROA Nonecovered by 155.92.0.0/16 670 100% 69
155.92.96.0/20 No ROA Nonecovered by 155.92.0.0/16 670 100% 69
155.92.192.0/18 No ROA Nonecovered by 155.92.0.0/16 670 100% 69
155.92.253.0/24 No ROA Nonecovered by 155.92.0.0/16 670 100% 69
155.92.0.0/16 No ROA Other IRR onlyRADB 670 100% 69

AS-SET

AS11500 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 29 are in fix.csv.

  • ROA: none8
  • Route object: none7
  • Route object: RIR1
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none155.92.0.0/18No ROA covers it. Add a ROA for AS11500, maxLength 18.670 of 673
Route object: none155.92.0.0/18No route object for it. A route object for 155.92.0.0/16 with origin AS11500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11500 in the RIR database for the space.670 of 673
ROA: none155.92.0.0/24No ROA covers it. Add a ROA for AS11500, maxLength 24.670 of 673
Route object: none155.92.0.0/24No route object for it. A route object for 155.92.0.0/16 with origin AS11500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11500 in the RIR database for the space.670 of 673
ROA: none155.92.11.0/24No ROA covers it. Add a ROA for AS11500, maxLength 24.670 of 673
Route object: none155.92.11.0/24No route object for it. A route object for 155.92.0.0/16 with origin AS11500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11500 in the RIR database for the space.670 of 673
ROA: none155.92.64.0/19No ROA covers it. Add a ROA for AS11500, maxLength 19.670 of 673
Route object: none155.92.64.0/19No route object for it. A route object for 155.92.0.0/16 with origin AS11500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11500 in the RIR database for the space.670 of 673
ROA: none155.92.96.0/20No ROA covers it. Add a ROA for AS11500, maxLength 20.670 of 673
Route object: none155.92.96.0/20No route object for it. A route object for 155.92.0.0/16 with origin AS11500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11500 in the RIR database for the space.670 of 673
ROA: none155.92.192.0/18No ROA covers it. Add a ROA for AS11500, maxLength 18.670 of 673
Route object: none155.92.192.0/18No route object for it. A route object for 155.92.0.0/16 with origin AS11500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11500 in the RIR database for the space.670 of 673
ROA: none155.92.253.0/24No ROA covers it. Add a ROA for AS11500, maxLength 24.670 of 673
Route object: none155.92.253.0/24No route object for it. A route object for 155.92.0.0/16 with origin AS11500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11500 in the RIR database for the space.670 of 673
ROA: none155.92.0.0/16No ROA covers it. Add a ROA for AS11500, maxLength 16.670 of 673
Route object: RIR155.92.0.0/16Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

63.163.134.0/24RADBNo ROA
198.17.174.0/24RADBNo ROA
199.165.157.0/24RADBNo ROA
204.94.146.0/24RADBNo ROA
206.168.104.0/21RADBNo ROA
207.174.123.0/24RADBNo ROA
207.174.158.0/24RADBNo ROA
207.174.206.0/23RADBNo ROA
207.174.207.0/24RADBNo ROA
207.174.224.0/21RADBNo ROA
207.174.224.0/24RADBNo ROA
207.174.225.0/24RADBNo ROA
207.174.226.0/24RADBNo 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.