bgpreport

Network · data from 2026-11-12

AS17207 Colorado College

Registry name: COLOR-COLL - Colorado College, US · PeeringDB

11IPv4 routes 72.7% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
3No 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 AS17207, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS17207, 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.
192.70.253.0/24 No ROA Other IRR onlyRADB 668 99% 68
192.188.250.0/24 No ROA Other IRR onlyRADB 668 99% 68
198.62.148.0/22 No ROA Other IRR onlyRADB 668 99% 68
198.59.3.0/24 Valid Other IRR onlyRADB 668 99% 68
198.59.4.0/24 Valid Other IRR onlyRADB 668 99% 68
198.59.5.0/24 Valid Other IRR onlyRADB 668 99% 68
198.59.6.0/24 Valid Other IRR onlyRADB 668 99% 68
204.228.84.0/24 Valid Other IRR onlyRADB 668 99% 68
204.228.85.0/24 Valid Other IRR onlyRADB 668 99% 68
204.228.86.0/24 Valid Other IRR onlyRADB 668 99% 68
204.228.87.0/24 Valid Other IRR onlyRADB 668 99% 68

AS-SET

AS17207'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 15 are in fix.csv.

  • ROA: none3
  • Route object: RIR11
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none192.70.253.0/24No ROA covers it. Add a ROA for AS17207, maxLength 24.668 of 673
Route object: RIR192.70.253.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none192.188.250.0/24No ROA covers it. Add a ROA for AS17207, maxLength 24.668 of 673
Route object: RIR192.188.250.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none198.62.148.0/22No ROA covers it. Add a ROA for AS17207, maxLength 22.668 of 673
Route object: RIR198.62.148.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR198.59.3.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR198.59.4.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR198.59.5.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR198.59.6.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR204.228.84.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR204.228.85.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR204.228.86.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR204.228.87.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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

205.170.0.0/20RADBNo 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.