bgpreport

Network · data from 2026-11-12

AS38 UIUC

Registry name: UIUC - University of Illinois, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38, 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.
72.36.64.0/18 No ROA Other IRR onlyRADB 670 100% 69
128.174.0.0/16 No ROA Other IRR onlyRADB 670 100% 69
130.126.0.0/16 No ROA Other IRR onlyRADB 670 100% 69
192.17.0.0/16 No ROA Other IRR onlyRADB 670 100% 69
2620:0:e00::/48 No ROA Other IRR onlyRADB 635 100% 70
2620:0:e01::/48 No ROA Other IRR onlyRADB 635 100% 70
2600:3900::/28 No ROA Other IRR onlyRADB 634 100% 70
72.36.80.0/23 No ROA Other IRR onlyRADB 19 3%low visibility 18
72.36.96.0/20 No ROA Other IRR onlyRADB 19 3%low visibility 18
72.36.97.0/26 No ROA Other IRR onlyRADB 7 1%low visibility 10

AS-SET

AS38'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 28 are in fix.csv.

  • ROA: none10
  • Route object: RIR10
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none72.36.64.0/18No ROA covers it. Add a ROA for AS38, maxLength 18.670 of 673
Route object: RIR72.36.64.0/18Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none128.174.0.0/16No ROA covers it. Add a ROA for AS38, maxLength 16.670 of 673
Route object: RIR128.174.0.0/16Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none130.126.0.0/16No ROA covers it. Add a ROA for AS38, maxLength 16.670 of 673
Route object: RIR130.126.0.0/16Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.17.0.0/16No ROA covers it. Add a ROA for AS38, maxLength 16.670 of 673
Route object: RIR192.17.0.0/16Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2620:0:e00::/48No ROA covers it. Add a ROA for AS38, maxLength 48.635 of 636
Route object: RIR2620:0:e00::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2620:0:e01::/48No ROA covers it. Add a ROA for AS38, maxLength 48.635 of 636
Route object: RIR2620:0:e01::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2600:3900::/28No ROA covers it. Add a ROA for AS38, maxLength 28.634 of 636
Route object: RIR2600:3900::/28Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none72.36.80.0/23No ROA covers it. Add a ROA for AS38, maxLength 23.19 of 673
Route object: RIR72.36.80.0/23Route object only in RADB. Add it in the RIR database for the space.19 of 673
ROA: none72.36.96.0/20No ROA covers it. Add a ROA for AS38, maxLength 20.19 of 673
Route object: RIR72.36.96.0/20Route object only in RADB. Add it in the RIR database for the space.19 of 673
ROA: none72.36.97.0/26No ROA covers it. Add a ROA for AS38, maxLength 26.7 of 673
Route object: RIR72.36.97.0/26Route object only in RADB. Add it in the RIR database for the space.7 of 673

Route objects not announced

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

72.36.64.160/27RADBNo ROA
72.36.81.64/26RADBNo ROA
72.36.84.0/22RADBNo ROA
72.36.88.0/24RADBNo ROA
72.36.91.0/27RADBNo ROA
72.36.96.0/24RADBNo ROA
72.36.100.0/22RADBNo ROA
72.36.104.0/21RADBNo 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.