bgpreport

Network · data from 2026-11-12

AS12816 MWN-AS Leibniz-Rechenzentrum

Registry name: MWN-AS Leibniz-Rechenzentrum, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS12816, 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.
138.244.0.0/15 No ROA RIR databaseRIPE 672 100% 68
192.54.42.0/24 No ROA RIR databaseRIPE 672 100% 68
192.129.1.0/24 No ROA RIR databaseRIPE 672 100% 68
138.246.0.0/16 No ROA RIR databaseRIPE 669 99% 68
129.187.0.0/16 Valid RIR databaseRIPE 672 100% 68
141.40.0.0/16 Valid RIR databaseRIPE 672 100% 68
141.84.0.0/16 Valid RIR databaseRIPE 672 100% 68
192.68.211.0/24 Valid RIR databaseRIPE 672 100% 68
192.68.212.0/22 Valid RIR databaseRIPE 672 100% 68
2001:4ca0::/29 Valid RIR databaseRIPE 635 100% 68

AS-SET

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

  • ROA: none4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none138.244.0.0/15No ROA covers it. Add a ROA for AS12816, maxLength 15.672 of 673
ROA: none192.54.42.0/24No ROA covers it. Add a ROA for AS12816, maxLength 24.672 of 673
ROA: none192.129.1.0/24No ROA covers it. Add a ROA for AS12816, maxLength 24.672 of 673
ROA: none138.246.0.0/16No ROA covers it. Add a ROA for AS12816, maxLength 16.669 of 673

Route objects not announced

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

192.44.30.0/23RIPEInvalid: origin
192.55.197.0/24RIPENo ROA
2001:4ca0::/32RIPEValid

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.