bgpreport

Network · data from 2026-11-12

AS14579 EDWARDJONES - Edward D. Jones & Co., L.P.

Registry name: EDWARDJONES - Edward D. Jones & Co., L.P., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS14579, 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.
167.80.0.0/16 Valid None 673 100% 67
167.80.64.0/18 Valid None 673 100% 67
167.80.77.0/24 Valid None 673 100% 67
167.80.128.0/18 Valid None 673 100% 67
167.80.149.0/24 Valid None 673 100% 67
167.80.177.0/24 Valid None 673 100% 67
167.80.196.0/24 Valid None 673 100% 67
167.80.244.0/24 Valid None 673 100% 67
167.80.246.0/24 Valid None 673 100% 67
167.80.102.0/24 Valid None 672 100% 67
167.80.134.0/24 Valid None 672 100% 67
167.80.248.0/24 Valid Other IRR onlyRADB 672 100% 67

AS-SET

AS14579 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 12 are in fix.csv.

  • Route object: none11
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
Route object: none167.80.0.0/16No route object for it. Add a route object with origin AS14579 in the RIR database for the space.673 of 673
Route object: none167.80.64.0/18No route object for it. Add a route object with origin AS14579 in the RIR database for the space.673 of 673
Route object: none167.80.77.0/24No route object for it. Add a route object with origin AS14579 in the RIR database for the space.673 of 673
Route object: none167.80.128.0/18No route object for it. Add a route object with origin AS14579 in the RIR database for the space.673 of 673
Route object: none167.80.149.0/24No route object for it. Add a route object with origin AS14579 in the RIR database for the space.673 of 673
Route object: none167.80.177.0/24No route object for it. Add a route object with origin AS14579 in the RIR database for the space.673 of 673
Route object: none167.80.196.0/24No route object for it. Add a route object with origin AS14579 in the RIR database for the space.673 of 673
Route object: none167.80.244.0/24No route object for it. Add a route object with origin AS14579 in the RIR database for the space.673 of 673
Route object: none167.80.246.0/24No route object for it. Add a route object with origin AS14579 in the RIR database for the space.673 of 673
Route object: none167.80.102.0/24No route object for it. Add a route object with origin AS14579 in the RIR database for the space.672 of 673
Route object: none167.80.134.0/24No route object for it. Add a route object with origin AS14579 in the RIR database for the space.672 of 673
Route object: RIR167.80.248.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS14579 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.