bgpreport

Network · data from 2026-11-12

AS31241 ASP-BE-AS ASP SA

Registry name: ASP-BE-AS ASP SA, BE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS31241, 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.65.135.0/24 No ROA Nonecovered by 80.65.128.0/20 672 100% 67
80.65.134.0/24 No ROA Nonecovered by 80.65.128.0/20 667 99% 67
80.65.128.0/20 No ROA RIR databaseRIPE 673 100% 67
2a00:c1c0::/32 No ROA RIR databaseRIPE 635 100% 67
80.65.128.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
80.65.129.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
80.65.131.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2

AS-SET

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

  • ROA: none7
  • Route object: none2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none80.65.135.0/24No ROA covers it. Add a ROA for AS31241, maxLength 24.672 of 673
Route object: none80.65.135.0/24No route object for it. A route object for 80.65.128.0/20 with origin AS31241 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31241 in the RIR database for the space.672 of 673
ROA: none80.65.134.0/24No ROA covers it. Add a ROA for AS31241, maxLength 24.667 of 673
Route object: none80.65.134.0/24No route object for it. A route object for 80.65.128.0/20 with origin AS31241 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31241 in the RIR database for the space.667 of 673
ROA: none80.65.128.0/20No ROA covers it. Add a ROA for AS31241, maxLength 20.673 of 673
ROA: none2a00:c1c0::/32No ROA covers it. Add a ROA for AS31241, maxLength 32.635 of 636
ROA: none80.65.128.0/24No ROA covers it. Add a ROA for AS31241, maxLength 24.2 of 673
ROA: none80.65.129.0/24No ROA covers it. Add a ROA for AS31241, maxLength 24.2 of 673
ROA: none80.65.131.0/24No ROA covers it. Add a ROA for AS31241, maxLength 24.2 of 673

Route objects not announced

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

80.65.130.0/24RIPENo ROA
80.65.132.0/24RIPENo ROA
80.65.133.0/24RIPENo ROA
80.65.136.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.