Autonomous system
AS12816 MWN-AS
Hosting APNIC
Summary
Leibniz-Rechenzentrum (Munich Scientific Network)
education research infrastructure
395,008 addresses, four legacy /16s, an IPv6 /29, and two BGP neighbours.
What it's used for
- The shared network of the Munich universities and research institutes, run by a Bavarian academic computing centre. 395,008 addresses across nine IPv4 prefixes, one IPv6 prefix, and two observed BGP neighbours.
Notable
- The large blocks are
138.244.0.0/15,129.187.0.0/16,138.246.0.0/16,141.40.0.0/16and141.84.0.0/16, alongside192.68.212.0/22,192.68.211.0/24,192.54.42.0/24and192.129.1.0/24. - Netnames include
LRZ-MUNICH-NET,LRZ-MUNICH,LRZ-NET,LRZ-NET1,LRZ-WEIHSTEPH,LMU-WIFO-INK,BL-NFS-LANandMPISOC-LAN. - IPv6 is
2001:4ca0::/29. - The registry lookup for
138.244.0.0/15failed, so nothing here describes that block's record. - Eighteen addresses were sampled and none returned a name.
Interesting
- Four /16s and a /15 is the address footprint of an organisation that was on the internet before addresses were rationed. Universities received space by asking for it, and those allocations are larger than anything a comparable institution could obtain today.
- The netnames read as a campus directory: a main site, an agricultural campus, a faculty institute, a Max Planck institute, and a LAN named after the file-sharing protocol it was built for. This is not one network but a federation, and the registry preserves the seams.
2001:4ca0::/29is eight times the size of the /32 most networks receive. National research networks are allocated as if they were registries themselves, because they hand space onward to member institutions.- Two neighbours for 395,008 addresses is the signature of academic networking: research traffic moves over a dedicated national backbone rather than commercial transit, so the whole federation reaches the wider internet through very few doors.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Transit providers
1 upstream, 1 downstream and 4 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS680 | Verein zur Foerderung eines Deutschen Forschungsnetzes e.V. | 593 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-10, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 9 prefixes · 395K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| DE | Germany | 10 |
Registry
Allocation record
- Registry
- APNIC
- Handle
AS12816- Registry name
- MWN-AS
- Registrant
- LRZ-MNT
- Abuse contact
- abuse@lrz.de
- Registered
- 2002-10-21
- Last changed
- 2019-06-19
- Allocation
- allocated
Routing security
RPKI and IRR
- RPKI
- 60% valid · 6 valid, 4 with no ROA
- ROAs
- 6 authorising AS12816
- ASPA
- 2 declared providers
- IRR
- 100% registered · 10 of 10 announcements
- Route objects
- 13 naming AS12816
Reputation
Classification and threat
Hosting Datacenter or cloud provider. Addresses are servers, not people.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 431 networks and 1,775 prefixes, as published 2026-10-11. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere