bgpreport

Network · data from 2026-11-12

AS12991 Land-OOE Amt der Ooe. Landesregierung

Registry name: Land-OOE Amt der Ooe. Landesregierung, AT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS12991, 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.
2001:628:2020::/48 Invalid: origin RIR databaseRIPE 1 0%low visibility 1
194.48.4.0/22 No ROA RIR databaseRIPE 670 100% 69
194.48.32.0/19 No ROA RIR databaseRIPE 670 100% 69
194.48.64.0/22 No ROA RIR databaseRIPE 670 100% 69
2001:67c:148::/48 No ROA RIR databaseRIPE 636 100% 70

AS-SET

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

  • ROA: origin1
  • ROA: none4
ChangePrefix or setDetailFull-table peers
ROA: origin2001:628:2020::/48ROAs covering it name AS1853, not AS12991. If AS12991 should announce it, add a ROA for AS12991.1 of 636
ROA: none194.48.4.0/22No ROA covers it. Add a ROA for AS12991, maxLength 22.670 of 673
ROA: none194.48.32.0/19No ROA covers it. Add a ROA for AS12991, maxLength 19.670 of 673
ROA: none194.48.64.0/22No ROA covers it. Add a ROA for AS12991, maxLength 22.670 of 673
ROA: none2001:67c:148::/48No ROA covers it. Add a ROA for AS12991, maxLength 48.636 of 636

Route objects not announced

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