bgpreport

Network · data from 2026-11-12

AS104 University of Colorado at Boulder

Registry name: COLORADO-AS - University of Colorado at Boulder, US · PeeringDB

21IPv4 routes 9.5% RPKI valid · 100.0% with a route object
4IPv6 routes 25.0% RPKI valid · 25.0% with a route object
2RPKI invalid 2 origin · 0 maxLength
20No ROA 3 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS104, seen from no peer

Announced routes

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

2401:eee0:1c0::/42 Invalid: origin None 86 14% 42
2401:eee0:200::/42 Invalid: origin None 86 14% 42
204.228.80.0/24 No ROA Other IRR onlyRADB 673 100% 67
128.138.0.0/16 No ROA Other IRR onlyRADB 670 100% 68
198.11.16.0/20 No ROA Other IRR onlyRADB 670 100% 68
146.5.20.0/22 No ROA Other IRR onlyRADB 668 99% 68
192.12.238.0/24 No ROA Other IRR onlyRADB 668 99% 68
192.12.240.0/24 No ROA Other IRR onlyRADB 668 99% 68
192.12.241.0/24 No ROA Other IRR onlyRADB 668 99% 68
192.12.242.0/24 No ROA Other IRR onlyRADB 668 99% 68
192.12.244.0/24 No ROA Other IRR onlyRADB 668 99% 68
192.12.245.0/24 No ROA Other IRR onlyRADB 668 99% 68
198.59.7.0/24 No ROA Other IRR onlyRADB 668 99% 68
198.59.51.0/24 No ROA Other IRR onlyRADB 668 99% 68
198.59.52.0/24 No ROA Other IRR onlyRADB 668 99% 68
198.59.54.0/24 No ROA Other IRR onlyRADB 668 99% 68
198.59.55.0/24 No ROA Other IRR onlyRADB 668 99% 68
198.59.70.0/24 No ROA Other IRR onlyRADB 668 99% 68
198.59.81.0/24 No ROA Other IRR onlyRADB 668 99% 68
198.59.82.0/24 No ROA Other IRR onlyRADB 668 99% 68
198.59.83.0/24 No ROA Other IRR onlyRADB 668 99% 68
2620:18f::/32 No ROA Other IRR onlyRADB 636 100% 68
2001:468:501::/48 Valid None 17 3%low visibility 18
129.19.240.0/20 Valid RIR databaseARIN, RADB 673 100% 68
129.19.192.0/18 Valid RIR databaseARIN, RADB 670 100% 68

AS-SET

AS104'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 52 are in fix.csv.

  • ROA: origin2
  • ROA: none20
  • Route object: none3
  • Route object: RIR20
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: origin2401:eee0:1c0::/42ROAs covering it name AS149433, not AS104. If AS104 should announce it, add a ROA for AS104.86 of 636
Route object: none2401:eee0:1c0::/42No route object for it. Add a route object with origin AS104 in the RIR database for the space.86 of 636
ROA: origin2401:eee0:200::/42ROAs covering it name AS149433, not AS104. If AS104 should announce it, add a ROA for AS104.86 of 636
Route object: none2401:eee0:200::/42No route object for it. Add a route object with origin AS104 in the RIR database for the space.86 of 636
ROA: none204.228.80.0/24No ROA covers it. Add a ROA for AS104, maxLength 24.673 of 673
Route object: RIR204.228.80.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none128.138.0.0/16No ROA covers it. Add a ROA for AS104, maxLength 16.670 of 673
Route object: RIR128.138.0.0/16Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none198.11.16.0/20No ROA covers it. Add a ROA for AS104, maxLength 20.670 of 673
Route object: RIR198.11.16.0/20Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none146.5.20.0/22No ROA covers it. Add a ROA for AS104, maxLength 22.668 of 673
Route object: RIR146.5.20.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none192.12.238.0/24No ROA covers it. Add a ROA for AS104, maxLength 24.668 of 673
Route object: RIR192.12.238.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none192.12.240.0/24No ROA covers it. Add a ROA for AS104, maxLength 24.668 of 673
Route object: RIR192.12.240.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none192.12.241.0/24No ROA covers it. Add a ROA for AS104, maxLength 24.668 of 673
Route object: RIR192.12.241.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none192.12.242.0/24No ROA covers it. Add a ROA for AS104, maxLength 24.668 of 673
Route object: RIR192.12.242.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none192.12.244.0/24No ROA covers it. Add a ROA for AS104, maxLength 24.668 of 673
Route object: RIR192.12.244.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none192.12.245.0/24No ROA covers it. Add a ROA for AS104, maxLength 24.668 of 673
Route object: RIR192.12.245.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none198.59.7.0/24No ROA covers it. Add a ROA for AS104, maxLength 24.668 of 673
Route object: RIR198.59.7.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none198.59.51.0/24No ROA covers it. Add a ROA for AS104, maxLength 24.668 of 673
Route object: RIR198.59.51.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none198.59.52.0/24No ROA covers it. Add a ROA for AS104, maxLength 24.668 of 673
Route object: RIR198.59.52.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none198.59.54.0/24No ROA covers it. Add a ROA for AS104, maxLength 24.668 of 673
Route object: RIR198.59.54.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none198.59.55.0/24No ROA covers it. Add a ROA for AS104, maxLength 24.668 of 673
Route object: RIR198.59.55.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none198.59.70.0/24No ROA covers it. Add a ROA for AS104, maxLength 24.668 of 673
Route object: RIR198.59.70.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none198.59.81.0/24No ROA covers it. Add a ROA for AS104, maxLength 24.668 of 673
Route object: RIR198.59.81.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none198.59.82.0/24No ROA covers it. Add a ROA for AS104, maxLength 24.668 of 673
Route object: RIR198.59.82.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none198.59.83.0/24No ROA covers it. Add a ROA for AS104, maxLength 24.668 of 673
Route object: RIR198.59.83.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none2620:18f::/32No ROA covers it. Add a ROA for AS104, maxLength 32.636 of 636
Route object: RIR2620:18f::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: none2001:468:501::/48No route object for it. Add a route object with origin AS104 in the RIR database for the space.17 of 636

Route objects not announced

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

146.5.20.0/24RADBNo ROA
192.12.239.0/24RADBNo ROA
192.12.243.0/24RADBNo ROA
192.12.246.0/24RADBNo ROA
198.59.61.0/24RADBNo ROA
198.118.206.0/24RADBNo ROA
204.228.67.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.