bgpreport

Network · data from 2026-11-12

AS49474 ALELM Elm Company PJS

Registry name: ALELM Elm Company PJS, SA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS49474, 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.
185.131.98.0/24 No ROA RIR databaseRADB, RIPE 673 100% 67
185.131.99.0/24 No ROA RIR databaseRIPE 673 100% 67
195.170.180.0/24 No ROA RIR databaseRIPE 672 100% 67
2a0c:cfc0:1::/48 No ROA RIR databaseRIPE 636 100% 67
2a0c:cfc0:2::/48 No ROA RIR databaseRIPE 636 100% 68
2a0c:cfc0:3::/48 No ROA RIR databaseRIPE 636 100% 67

AS-SET

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

  • ROA: none6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none185.131.98.0/24No ROA covers it. Add a ROA for AS49474, maxLength 24.673 of 673
ROA: none185.131.99.0/24No ROA covers it. Add a ROA for AS49474, maxLength 24.673 of 673
ROA: none195.170.180.0/24No ROA covers it. Add a ROA for AS49474, maxLength 24.672 of 673
ROA: none2a0c:cfc0:1::/48No ROA covers it. Add a ROA for AS49474, maxLength 48.636 of 636
ROA: none2a0c:cfc0:2::/48No ROA covers it. Add a ROA for AS49474, maxLength 48.636 of 636
ROA: none2a0c:cfc0:3::/48No ROA covers it. Add a ROA for AS49474, maxLength 48.636 of 636

Route objects not announced

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

185.131.98.0/23RIPENo 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.