bgpreport

Network · data from 2026-11-12

AS51482 Banedanmark-AS Banedanmark

Registry name: Banedanmark-AS Banedanmark, DK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS51482, 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.243.120.0/24 Invalid: origin None 2 0%low visibility 1
91.216.101.0/24 No ROA RIR databaseRIPE 673 100% 66

AS-SET

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

  • ROA: origin1
  • ROA: none1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin80.243.120.0/24ROAs covering it name AS31027, not AS51482. If AS51482 should announce it, add a ROA for AS51482.2 of 673
Route object: none80.243.120.0/24No route object for it. Add a route object with origin AS51482 in the RIR database for the space.2 of 673
ROA: none91.216.101.0/24No ROA covers it. Add a ROA for AS51482, maxLength 24.673 of 673

Route objects not announced

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