bgpreport

Network · data from 2026-11-12

AS44741 ALENANET

Registry name: ALENANET Alena Net SRL, IT · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS44741, 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.
92.39.144.0/24 No ROA RIR databaseRIPE 673 100% 67
92.39.145.0/24 No ROA RIR databaseRIPE 673 100% 67
92.39.146.0/24 No ROA RIR databaseRIPE 673 100% 67
92.39.147.0/24 No ROA RIR databaseRIPE 673 100% 67
92.39.148.0/24 No ROA RIR databaseRIPE 673 100% 67
92.39.151.0/24 No ROA RIR databaseRIPE 673 100% 67
92.39.152.0/24 No ROA RIR databaseRIPE 673 100% 67
92.39.153.0/24 No ROA RIR databaseRIPE 673 100% 67
92.39.154.0/24 No ROA RIR databaseRIPE 673 100% 67
92.39.155.0/24 No ROA RIR databaseRIPE 673 100% 67
92.39.156.0/24 No ROA RIR databaseRIPE 673 100% 67
92.39.157.0/24 No ROA RIR databaseRIPE 673 100% 67
92.39.158.0/24 No ROA RIR databaseRIPE 673 100% 67
92.39.159.0/24 No ROA RIR databaseRIPE 673 100% 67

AS-SET

AS44741's PeeringDB record names no 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 25 are in fix.csv.

  • ROA: none14
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none92.39.144.0/24No ROA covers it. Add a ROA for AS44741, maxLength 24.673 of 673
ROA: none92.39.145.0/24No ROA covers it. Add a ROA for AS44741, maxLength 24.673 of 673
ROA: none92.39.146.0/24No ROA covers it. Add a ROA for AS44741, maxLength 24.673 of 673
ROA: none92.39.147.0/24No ROA covers it. Add a ROA for AS44741, maxLength 24.673 of 673
ROA: none92.39.148.0/24No ROA covers it. Add a ROA for AS44741, maxLength 24.673 of 673
ROA: none92.39.151.0/24No ROA covers it. Add a ROA for AS44741, maxLength 24.673 of 673
ROA: none92.39.152.0/24No ROA covers it. Add a ROA for AS44741, maxLength 24.673 of 673
ROA: none92.39.153.0/24No ROA covers it. Add a ROA for AS44741, maxLength 24.673 of 673
ROA: none92.39.154.0/24No ROA covers it. Add a ROA for AS44741, maxLength 24.673 of 673
ROA: none92.39.155.0/24No ROA covers it. Add a ROA for AS44741, maxLength 24.673 of 673
ROA: none92.39.156.0/24No ROA covers it. Add a ROA for AS44741, maxLength 24.673 of 673
ROA: none92.39.157.0/24No ROA covers it. Add a ROA for AS44741, maxLength 24.673 of 673
ROA: none92.39.158.0/24No ROA covers it. Add a ROA for AS44741, maxLength 24.673 of 673
ROA: none92.39.159.0/24No ROA covers it. Add a ROA for AS44741, maxLength 24.673 of 673

Route objects not announced

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

92.39.144.0/22RIPENo ROA
92.39.149.0/24RIPENo ROA
92.39.150.0/24RIPENo ROA
2a07:b840::/32RIPENo ROA
2a07:b841::/32RIPENo ROA
2a07:b842::/32RIPENo ROA
2a07:b843::/32RIPENo ROA
2a07:b844::/32RIPENo ROA
2a07:b845::/32RIPENo ROA
2a07:b846::/32RIPENo ROA
2a07:b847::/32RIPENo 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.