bgpreport

Network · data from 2026-11-12

AS11719 EATON-CORPORATION - Eaton Corporation

Registry name: EATON-CORPORATION - Eaton Corporation, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS11719, 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.

148.179.0.0/16 No ROA None 672 100% 67
151.110.0.0/16 No ROA None 672 100% 67
166.99.0.0/16 No ROA None 672 100% 67
192.31.41.0/24 No ROA None 672 100% 67
192.104.67.0/24 No ROA None 672 100% 67
199.255.204.0/24 No ROA None 672 100% 67
199.255.205.0/24 No ROA None 672 100% 67
199.255.206.0/24 No ROA None 672 100% 67
199.255.207.0/24 No ROA None 672 100% 67

AS-SET

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

  • ROA: none9
  • Route object: none9
ChangePrefix or setDetailFull-table peers
ROA: none148.179.0.0/16No ROA covers it. Add a ROA for AS11719, maxLength 16.672 of 673
Route object: none148.179.0.0/16No route object for it. Add a route object with origin AS11719 in the RIR database for the space.672 of 673
ROA: none151.110.0.0/16No ROA covers it. Add a ROA for AS11719, maxLength 16.672 of 673
Route object: none151.110.0.0/16No route object for it. Add a route object with origin AS11719 in the RIR database for the space.672 of 673
ROA: none166.99.0.0/16No ROA covers it. Add a ROA for AS11719, maxLength 16.672 of 673
Route object: none166.99.0.0/16No route object for it. Add a route object with origin AS11719 in the RIR database for the space.672 of 673
ROA: none192.31.41.0/24No ROA covers it. Add a ROA for AS11719, maxLength 24.672 of 673
Route object: none192.31.41.0/24No route object for it. Add a route object with origin AS11719 in the RIR database for the space.672 of 673
ROA: none192.104.67.0/24No ROA covers it. Add a ROA for AS11719, maxLength 24.672 of 673
Route object: none192.104.67.0/24No route object for it. Add a route object with origin AS11719 in the RIR database for the space.672 of 673
ROA: none199.255.204.0/24No ROA covers it. Add a ROA for AS11719, maxLength 24.672 of 673
Route object: none199.255.204.0/24No route object for it. Add a route object with origin AS11719 in the RIR database for the space.672 of 673
ROA: none199.255.205.0/24No ROA covers it. Add a ROA for AS11719, maxLength 24.672 of 673
Route object: none199.255.205.0/24No route object for it. Add a route object with origin AS11719 in the RIR database for the space.672 of 673
ROA: none199.255.206.0/24No ROA covers it. Add a ROA for AS11719, maxLength 24.672 of 673
Route object: none199.255.206.0/24No route object for it. Add a route object with origin AS11719 in the RIR database for the space.672 of 673
ROA: none199.255.207.0/24No ROA covers it. Add a ROA for AS11719, maxLength 24.672 of 673
Route object: none199.255.207.0/24No route object for it. Add a route object with origin AS11719 in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS11719 is announced.

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.