asn.dev

Routing security

AS12816 MWN-AS

Hosting APNIC

RPKI valid 60% 6 of 10 announcements
RPKI invalid 0 none
No ROA 4 not covered by any ROA
IRR registered 100% 0 missing · 0 other origin
ROAs 6 authorising this AS

Announcements

What this network originates

10 observed

Every prefix observed with AS12816 as its origin, checked against RPKI and the IRR. Problems sort first.

PrefixRPKIIRRVantage points
138.244.0.0/15No ROAIRR55
138.246.0.0/16No ROAIRR55
192.54.42.0/24No ROAIRR55
192.129.1.0/24No ROAIRR55
129.187.0.0/16RPKI validIRR55
141.40.0.0/16RPKI validIRR55
141.84.0.0/16RPKI validIRR55
192.68.211.0/24RPKI validIRR55
192.68.212.0/22RPKI validIRR55
2001:4ca0::/29RPKI validIRR31

RPKI · ROAs

Route origin authorisations

6 ROAs

Signed statements by address holders that AS12816 may originate these prefixes, up to the maximum length shown.

PrefixMax lengthTrust anchor
129.187.0.0/16/16RIPENCC
141.40.0.0/16/16RIPENCC
141.84.0.0/16/16RIPENCC
192.68.211.0/24/24RIPENCC
192.68.212.0/22/22RIPENCC
2001:4ca0::/29/32RIPENCC

ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.

RPKI · ASPA

Declared transit providers

2 declared

This network has signed an ASPA record naming its transit providers. Each is compared against the upstreams observed in routing paths.

ASNetworkASPARouting paths
AS680Verein zur Foerderung eines Deutschen Forschungsnetzes e.V.DeclaredObserved
AS8767M-net Telekommunikations GmbHDeclarednot observed

An observed upstream that is not declared is not necessarily a leak: our upstream inference cannot tell a transit provider from a peer seen in the same position. A declared provider that is never observed is usually a backup path.

IRR

Registered route objects

13 objects · 3 not announced

Route objects naming AS12816 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.

PrefixSourceDescriptionMaintainerChangedRouting
192.44.30.0/23RIPEFHG-NET-AISEC-30FHG-MNT2012-02-02Not announced
192.55.197.0/24RIPELIS-NETLRZ-MNT2002-11-25Not announced
2001:4ca0::/32RIPELeibniz-Rechenzentrum MuenchenLRZ-MNT2005-05-25Not announced
129.187.0.0/16RIPELRZ-MUNICH-NETLRZ-MNT2002-11-25Announced
138.244.0.0/15RIPELMU-MEDVERLRZ-MNT2002-11-25Announced
138.246.0.0/16RIPELMU-WIFO-INKLRZ-MNT2002-11-25Announced
141.40.0.0/16RIPEDFN-AGG-44LRZ-MNT2002-11-25Announced
141.84.0.0/16RIPELRZ-MUNICHLRZ-MNT2002-11-25Announced
192.54.42.0/24RIPEBL-NFS-LANLRZ-MNT2002-11-25Announced
192.68.211.0/24RIPELRZ-NETLRZ-MNT2002-11-25Announced
192.68.212.0/22RIPELRZ-NETLRZ-MNT2002-11-25Announced
192.129.1.0/24RIPEMPIPF-LANDFN-LIR-MNT2024-10-31Announced
2001:4ca0::/29RIPELeibniz-Rechenzentrum MuenchenLRZ-MNT2017-04-13Announced

IRR

AS-sets

The as-set is what upstreams expand to build this network's customer filter. Sets that list AS12816 directly show who expects to carry it.

AS-setWhereRelationship
AS-MNETDERIPELists AS12816 as a direct member
AS-MWNRIPELists AS12816 as a direct member
AS680:AS-DFNTOWINISPRIPELists AS12816 as a direct member
AS8767:AS-DNSRIPELists AS12816 as a direct member

RPKI from rpki-client, validated 2026-10-12 12:10 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-12. Cross-check on bgp.he.net.