bgpreport

Network · data from 2026-11-12

AS200145 Aarhusnetwork Aarhus Kommune

Registry name: Aarhusnetwork Aarhus Kommune, DK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS200145, 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.155.134.0/24 No ROA Nonecovered by 185.155.132.0/22 673 100% 66
185.155.135.0/24 No ROA Nonecovered by 185.155.132.0/22 673 100% 66
185.155.132.0/22 No ROA RIR databaseRIPE 673 100% 66
185.155.132.0/24 No ROA RIR databaseRIPE 673 100% 66
185.155.133.0/24 No ROA RIR databaseRIPE 673 100% 66
193.33.148.0/23 No ROA RIR databaseRIPE 673 100% 66
193.33.148.0/24 No ROA RIR databaseRIPE 673 100% 66
193.33.149.0/24 No ROA RIR databaseRIPE 673 100% 66
193.105.220.0/24 No ROA RIR databaseRIPE 673 100% 66

AS-SET

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

  • ROA: none9
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none185.155.134.0/24No ROA covers it. Add a ROA for AS200145, maxLength 24.673 of 673
Route object: none185.155.134.0/24No route object for it. A route object for 185.155.132.0/22 with origin AS200145 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200145 in the RIR database for the space.673 of 673
ROA: none185.155.135.0/24No ROA covers it. Add a ROA for AS200145, maxLength 24.673 of 673
Route object: none185.155.135.0/24No route object for it. A route object for 185.155.132.0/22 with origin AS200145 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200145 in the RIR database for the space.673 of 673
ROA: none185.155.132.0/22No ROA covers it. Add a ROA for AS200145, maxLength 22.673 of 673
ROA: none185.155.132.0/24No ROA covers it. Add a ROA for AS200145, maxLength 24.673 of 673
ROA: none185.155.133.0/24No ROA covers it. Add a ROA for AS200145, maxLength 24.673 of 673
ROA: none193.33.148.0/23No ROA covers it. Add a ROA for AS200145, maxLength 23.673 of 673
ROA: none193.33.148.0/24No ROA covers it. Add a ROA for AS200145, maxLength 24.673 of 673
ROA: none193.33.149.0/24No ROA covers it. Add a ROA for AS200145, maxLength 24.673 of 673
ROA: none193.105.220.0/24No ROA covers it. Add a ROA for AS200145, maxLength 24.673 of 673

Route objects not announced

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