bgpreport

Network · data from 2026-11-12

AS40839 KOHLS-ECOM - KOHLS DEPARTMENT STORES

Registry name: KOHLS-ECOM - KOHLS DEPARTMENT STORES, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS40839, 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.
66.232.224.0/24 No ROA RIR databaseARIN 673 100% 67
66.232.226.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
66.232.227.0/24 No ROA RIR databaseARIN 673 100% 67
66.232.228.0/23 No ROA RIR databaseARIN 673 100% 67
66.232.228.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
66.232.231.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
66.232.232.0/21 No ROA RIR databaseARIN, RADB 673 100% 67
66.232.232.0/22 No ROA RIR databaseARIN, RADB 673 100% 67
66.232.236.0/22 No ROA RIR databaseARIN 673 100% 67
66.232.226.0/23 No ROA RIR databaseARIN 672 100% 67
66.232.229.0/24 No ROA RIR databaseARIN, RADB 2 0%low visibility 2

AS-SET

AS40839 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 14 are in fix.csv.

  • ROA: none11
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none66.232.224.0/24No ROA covers it. Add a ROA for AS40839, maxLength 24.673 of 673
ROA: none66.232.226.0/24No ROA covers it. Add a ROA for AS40839, maxLength 24.673 of 673
ROA: none66.232.227.0/24No ROA covers it. Add a ROA for AS40839, maxLength 24.673 of 673
ROA: none66.232.228.0/23No ROA covers it. Add a ROA for AS40839, maxLength 23.673 of 673
ROA: none66.232.228.0/24No ROA covers it. Add a ROA for AS40839, maxLength 24.673 of 673
ROA: none66.232.231.0/24No ROA covers it. Add a ROA for AS40839, maxLength 24.673 of 673
ROA: none66.232.232.0/21No ROA covers it. Add a ROA for AS40839, maxLength 21.673 of 673
ROA: none66.232.232.0/22No ROA covers it. Add a ROA for AS40839, maxLength 22.673 of 673
ROA: none66.232.236.0/22No ROA covers it. Add a ROA for AS40839, maxLength 22.673 of 673
ROA: none66.232.226.0/23No ROA covers it. Add a ROA for AS40839, maxLength 23.672 of 673
ROA: none66.232.229.0/24No ROA covers it. Add a ROA for AS40839, maxLength 24.2 of 673

Route objects not announced

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

66.232.224.0/20ARINNo ROA
66.232.225.0/24ARINNo ROA
66.232.230.0/24ARIN, 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.