bgpreport

Network · data from 2026-11-12

AS698 ASN-UIUC-REGION-AS - University of Illinois

Registry name: ASN-UIUC-REGION-AS - University of Illinois, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS698, 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.22.176.0/21 No ROA Nonecovered by 64.22.176.0/20 1 0%low visibility 1
64.22.184.0/21 No ROA Nonecovered by 64.22.176.0/20 1 0%low visibility 1
64.22.188.194/32 No ROA Nonecovered by 64.22.176.0/20 1 0%low visibility 1
64.22.188.195/32 No ROA Nonecovered by 64.22.176.0/20 1 0%low visibility 1
204.93.0.0/20 No ROA Nonecovered by 204.93.0.0/19 1 0%low visibility 1
204.93.0.71/32 No ROA Nonecovered by 204.93.0.0/19 1 0%low visibility 1
204.93.0.72/32 No ROA Nonecovered by 204.93.0.0/19 1 0%low visibility 1
204.93.20.0/23 No ROA Nonecovered by 204.93.0.0/19 1 0%low visibility 1
204.93.22.0/23 No ROA Nonecovered by 204.93.0.0/19 1 0%low visibility 1
204.93.24.0/21 No ROA Nonecovered by 204.93.0.0/19 1 0%low visibility 1
64.22.176.0/20 No ROA Other IRR onlyRADB 670 100% 69
204.93.0.0/19 No ROA Other IRR onlyRADB 670 100% 69
2620:79:8000::/48 No ROA Other IRR onlyRADB 635 100% 70

AS-SET

AS698 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 26 are in fix.csv.

  • ROA: none13
  • Route object: none10
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none64.22.176.0/21No ROA covers it. Add a ROA for AS698, maxLength 21.1 of 673
Route object: none64.22.176.0/21No route object for it. A route object for 64.22.176.0/20 with origin AS698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS698 in the RIR database for the space.1 of 673
ROA: none64.22.184.0/21No ROA covers it. Add a ROA for AS698, maxLength 21.1 of 673
Route object: none64.22.184.0/21No route object for it. A route object for 64.22.176.0/20 with origin AS698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS698 in the RIR database for the space.1 of 673
ROA: none64.22.188.194/32No ROA covers it. Add a ROA for AS698, maxLength 32.1 of 673
Route object: none64.22.188.194/32No route object for it. A route object for 64.22.176.0/20 with origin AS698 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS698 in the RIR database for the space.1 of 673
ROA: none64.22.188.195/32No ROA covers it. Add a ROA for AS698, maxLength 32.1 of 673
Route object: none64.22.188.195/32No route object for it. A route object for 64.22.176.0/20 with origin AS698 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS698 in the RIR database for the space.1 of 673
ROA: none204.93.0.0/20No ROA covers it. Add a ROA for AS698, maxLength 20.1 of 673
Route object: none204.93.0.0/20No route object for it. A route object for 204.93.0.0/19 with origin AS698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS698 in the RIR database for the space.1 of 673
ROA: none204.93.0.71/32No ROA covers it. Add a ROA for AS698, maxLength 32.1 of 673
Route object: none204.93.0.71/32No route object for it. A route object for 204.93.0.0/19 with origin AS698 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS698 in the RIR database for the space.1 of 673
ROA: none204.93.0.72/32No ROA covers it. Add a ROA for AS698, maxLength 32.1 of 673
Route object: none204.93.0.72/32No route object for it. A route object for 204.93.0.0/19 with origin AS698 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS698 in the RIR database for the space.1 of 673
ROA: none204.93.20.0/23No ROA covers it. Add a ROA for AS698, maxLength 23.1 of 673
Route object: none204.93.20.0/23No route object for it. A route object for 204.93.0.0/19 with origin AS698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS698 in the RIR database for the space.1 of 673
ROA: none204.93.22.0/23No ROA covers it. Add a ROA for AS698, maxLength 23.1 of 673
Route object: none204.93.22.0/23No route object for it. A route object for 204.93.0.0/19 with origin AS698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS698 in the RIR database for the space.1 of 673
ROA: none204.93.24.0/21No ROA covers it. Add a ROA for AS698, maxLength 21.1 of 673
Route object: none204.93.24.0/21No route object for it. A route object for 204.93.0.0/19 with origin AS698 covers it (filters allowing more-specifics accept it). Add a route object with origin AS698 in the RIR database for the space.1 of 673
ROA: none64.22.176.0/20No ROA covers it. Add a ROA for AS698, maxLength 20.670 of 673
Route object: RIR64.22.176.0/20Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none204.93.0.0/19No ROA covers it. Add a ROA for AS698, maxLength 19.670 of 673
Route object: RIR204.93.0.0/19Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2620:79:8000::/48No ROA covers it. Add a ROA for AS698, maxLength 48.635 of 636
Route object: RIR2620:79:8000::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS698 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.