bgpreport

Network · data from 2026-11-12

AS21896 ALLIANT-ENERGY - Alliant Energy

Registry name: ALLIANT-ENERGY - Alliant Energy, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS21896, 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.
198.7.38.0/23 No ROA RIR databaseARIN, RADB 673 100% 67
198.7.42.0/23 No ROA RIR databaseARIN, RADB 673 100% 67
198.7.44.0/23 No ROA RIR databaseARIN, RADB 673 100% 67
198.7.46.0/23 No ROA RIR databaseARIN, RADB 673 100% 67
207.71.128.0/23 No ROA RIR databaseARIN, RADB 671 100% 68
207.71.134.0/23 No ROA RIR databaseARIN, RADB 671 100% 68
207.71.136.0/23 No ROA RIR databaseARIN, RADB 671 100% 68
207.71.142.0/23 No ROA RIR databaseARIN, RADB 671 100% 68

AS-SET

AS21896 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 29 are in fix.csv.

  • ROA: none8
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
ROA: none198.7.38.0/23No ROA covers it. Add a ROA for AS21896, maxLength 23.673 of 673
ROA: none198.7.42.0/23No ROA covers it. Add a ROA for AS21896, maxLength 23.673 of 673
ROA: none198.7.44.0/23No ROA covers it. Add a ROA for AS21896, maxLength 23.673 of 673
ROA: none198.7.46.0/23No ROA covers it. Add a ROA for AS21896, maxLength 23.673 of 673
ROA: none207.71.128.0/23No ROA covers it. Add a ROA for AS21896, maxLength 23.671 of 673
ROA: none207.71.134.0/23No ROA covers it. Add a ROA for AS21896, maxLength 23.671 of 673
ROA: none207.71.136.0/23No ROA covers it. Add a ROA for AS21896, maxLength 23.671 of 673
ROA: none207.71.142.0/23No ROA covers it. Add a ROA for AS21896, maxLength 23.671 of 673

Route objects not announced

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

198.7.32.0/20ARIN, RADBNo ROA
198.7.38.0/24ARINNo ROA
198.7.39.0/24ARINNo ROA
198.7.42.0/24ARINNo ROA
198.7.43.0/24ARINNo ROA
198.7.44.0/24ARINNo ROA
198.7.45.0/24ARINNo ROA
198.7.46.0/24ARINNo ROA
198.7.47.0/24ARINNo ROA
198.7.48.0/21ARIN, RADBNo ROA
204.126.86.0/23ARINNo ROA
207.71.128.0/19ARIN, RADBNo ROA
207.71.128.0/24ARINNo ROA
207.71.129.0/24ARINNo ROA
207.71.134.0/24ARINNo ROA
207.71.135.0/24ARINNo ROA
207.71.136.0/24ARINNo ROA
207.71.137.0/24ARINNo ROA
207.71.142.0/24ARINNo ROA
207.71.143.0/24ARINNo ROA
207.71.176.0/20ARIN, RADBNo 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.