bgpreport

Network · data from 2026-11-12

AS34697 EMERSON-EMA-AS Emerson Electric UK Limited

Registry name: EMERSON-EMA-AS Emerson Electric UK Limited, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS34697, 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.
80.79.83.0/24 No ROA Nonecovered by 80.79.80.0/20 671 100% 67
80.79.80.0/20 No ROA RIR databaseRIPE 673 100% 70

AS-SET

AS34697 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.

  • ROA: none2
  • Route object: none1
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none80.79.83.0/24No ROA covers it. Add a ROA for AS34697, maxLength 24.671 of 673
Route object: none80.79.83.0/24No route object for it. A route object for 80.79.80.0/20 with origin AS34697 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34697 in the RIR database for the space.671 of 673
ROA: none80.79.80.0/20No ROA covers it. Add a ROA for AS34697, maxLength 20.673 of 673

Route objects not announced

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

80.79.80.0/24RIPENo ROA
80.79.81.0/24RIPENo ROA
80.79.82.0/24RIPENo ROA
80.79.84.0/24RIPENo ROA
80.79.85.0/24RIPENo ROA
80.79.86.0/24RIPENo ROA
80.79.87.0/24RIPENo ROA
80.79.90.0/24RIPENo ROA
80.79.91.0/24RIPENo 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.