AS209335 TUM-RBG Technical University of Munich
🇩🇪Org handle: ORG-TUM4-RIPE
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)66,560
Announced (BGP)66,560
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Routing hygiene
Score 10/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
Based on 3 announced prefixes, updated daily (2026-10-20). How the score works · RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 85.208.24.0/22 | 🇩🇪 DE | RIPENCC | allocated |
| 131.159.0.0/16 | 🇩🇪 DE | RIPENCC | assigned |
| 2a09:80c0::/29 | 🇩🇪 DE | RIPENCC | allocated |
All 3 announced prefixes of AS209335 →
Upstream Providers(1)
| ASN | Name |
|---|---|
| AS12816 | 🇩🇪MWN-AS Leibniz-Rechenzentrum |
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS209335 hands its own prefixes to: transit providers, or peers at an exchange.
- AS12816MWN Leibniz Rechenzentrum3
Abuse Contact
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- How to run an ASPA checkVerify the upstream providers listed above
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/209335Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/209335" | jq