bgpreport

Network · data from 2026-11-12

AS27595 Columbia College Chicago

Registry name: COLUM-600 - Columbia College Chicago, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS27595, 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.
199.168.232.0/22 No ROA Other IRR onlyRADB 667 99% 67
199.168.236.0/22 No ROA Other IRR onlyRADB 667 99% 67

AS-SET

AS27595'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 32 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced28
ChangePrefix or setDetailFull-table peers
ROA: none199.168.232.0/22No ROA covers it. Add a ROA for AS27595, maxLength 22.667 of 673
Route object: RIR199.168.232.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none199.168.236.0/22No ROA covers it. Add a ROA for AS27595, maxLength 22.667 of 673
Route object: RIR199.168.236.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673

Route objects not announced

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

58.65.238.0/24ALTDBNo ROA
58.65.239.0/24ALTDBNo ROA
64.28.176.0/20ALTDBNo ROA
67.130.99.0/24ALTDBNo ROA
67.210.8.0/22ALTDBNo ROA
67.210.13.0/24ALTDBNo ROA
67.210.14.0/23ALTDBNo ROA
69.1.78.0/24ALTDBNo ROA
69.22.162.0/23ALTDBNo ROA
69.22.168.0/22ALTDBNo ROA
69.22.184.0/22ALTDBNo ROA
116.50.10.0/24ALTDBNo ROA
116.50.11.0/24ALTDBNo ROA
195.95.218.0/23ALTDBNo ROA
199.168.232.0/21NTTCOMNo ROA
199.168.232.0/23RADBNo ROA
199.168.232.0/24RADBNo ROA
199.168.233.0/24RADBNo ROA
199.168.234.0/23RADBNo ROA
199.168.234.0/24RADBNo ROA
199.168.235.0/24RADBNo ROA
199.168.236.0/23RADBNo ROA
199.168.236.0/24RADBNo ROA
199.168.237.0/24RADBNo ROA
199.168.238.0/23RADBNo ROA
199.168.238.0/24RADBNo ROA
199.168.239.0/24RADBNo ROA
2620:62:8000::/48NTTCOMNo 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.