bgpreport

Network · data from 2026-11-12

AS1657 LOUISVILLE

Registry name: LOUISVILLE - University of Louisville, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS1657, 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.
2610:1e0:1800::/48 No ROA None 606 95% 68
136.165.0.0/16 No ROA RIR databaseARIN 673 100% 68
136.165.0.0/18 No ROA RIR databaseARIN 20 3%low visibility 18
136.165.0.0/19 No ROA RIR databaseARIN 20 3%low visibility 18
136.165.32.0/19 No ROA RIR databaseARIN 20 3%low visibility 18
136.165.64.0/18 No ROA RIR databaseARIN 20 3%low visibility 18
136.165.64.0/19 No ROA RIR databaseARIN 20 3%low visibility 18
136.165.96.0/19 No ROA RIR databaseARIN 20 3%low visibility 18
136.165.128.0/18 No ROA RIR databaseARIN 20 3%low visibility 18
136.165.128.0/19 No ROA RIR databaseARIN 20 3%low visibility 18
136.165.160.0/19 No ROA RIR databaseARIN 20 3%low visibility 18
136.165.192.0/18 No ROA RIR databaseARIN 20 3%low visibility 18
136.165.192.0/19 No ROA RIR databaseARIN 20 3%low visibility 18
136.165.224.0/19 No ROA RIR databaseARIN 20 3%low visibility 18
136.165.244.0/24 Valid RIR databaseARIN 670 100% 67

AS-SET

AS1657'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 18 are in fix.csv.

  • ROA: none14
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2610:1e0:1800::/48No ROA covers it. Add a ROA for AS1657, maxLength 48.606 of 636
Route object: none2610:1e0:1800::/48No route object for it. Add a route object with origin AS1657 in the RIR database for the space.606 of 636
ROA: none136.165.0.0/16No ROA covers it. Add a ROA for AS1657, maxLength 16.673 of 673
ROA: none136.165.0.0/18No ROA covers it. Add a ROA for AS1657, maxLength 18.20 of 673
ROA: none136.165.0.0/19No ROA covers it. Add a ROA for AS1657, maxLength 19.20 of 673
ROA: none136.165.32.0/19No ROA covers it. Add a ROA for AS1657, maxLength 19.20 of 673
ROA: none136.165.64.0/18No ROA covers it. Add a ROA for AS1657, maxLength 18.20 of 673
ROA: none136.165.64.0/19No ROA covers it. Add a ROA for AS1657, maxLength 19.20 of 673
ROA: none136.165.96.0/19No ROA covers it. Add a ROA for AS1657, maxLength 19.20 of 673
ROA: none136.165.128.0/18No ROA covers it. Add a ROA for AS1657, maxLength 18.20 of 673
ROA: none136.165.128.0/19No ROA covers it. Add a ROA for AS1657, maxLength 19.20 of 673
ROA: none136.165.160.0/19No ROA covers it. Add a ROA for AS1657, maxLength 19.20 of 673
ROA: none136.165.192.0/18No ROA covers it. Add a ROA for AS1657, maxLength 18.20 of 673
ROA: none136.165.192.0/19No ROA covers it. Add a ROA for AS1657, maxLength 19.20 of 673
ROA: none136.165.224.0/19No ROA covers it. Add a ROA for AS1657, maxLength 19.20 of 673

Route objects not announced

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

136.165.0.0/17ARINNo ROA
136.165.128.0/17ARINNo ROA
136.165.224.0/20ARINValid

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.