AS47132 INNONET-AS Innonet ICT-Services GmbH
🇦🇹Org handle: ORG-IIG12-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
16total
13 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)3,072
Announced (BGP)9,472
IPv6 Addresses
Allocated (RIR)1.2×10³⁰
Announced (BGP)1.2×10³⁰
Routing hygiene
Score 31/100 · Medium riskRPKI ROA coverage
31.3%
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
- 69% of announced prefixes (11 of 16) have no valid ROA
- Only one upstream seen in the AS paths of its routes
Based on 16 announced prefixes, updated daily (2026-10-23). How the score works · RPKI explained
Announced Prefixes
(BGP)16|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | Other IRR | 2026-10-26 | |
| No ROA | Other IRR | 2026-10-26 | |
| No ROA | - | 2026-10-26 | |
| No ROA | - | 2026-10-26 | |
| No ROA | - | 2026-10-26 | |
| No ROA | Other IRR | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| No ROA | RIPE | 2026-10-26 | |
| No ROA | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 |
1-10 of 16
1 / 2
Allocated Prefixes
(RIR)9Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.81.214.0/24 | 🇦🇹 AT | RIPE | assigned |
| 185.143.180.0/22 | 🇦🇹 AT | RIPENCC | allocated |
| 185.144.160.0/22 | 🇦🇹 AT | RIPENCC | allocated |
| 185.227.90.0/24 | 🇦🇹 AT | RIPE | assigned |
| 213.208.145.0/24 | 🇦🇹 AT | RIPE | assigned |
| 213.208.146.0/24 | 🇦🇹 AT | RIPE | assigned |
| 2001:978:900::/48 | 🇩🇪 DE | RIPE | assigned |
| 2a07:3740::/29 | 🇦🇹 AT | RIPENCC | allocated |
| 2a07:4080::/29 | 🇦🇹 AT | RIPENCC | allocated |
All 16 announced prefixes of AS47132 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS47132 hands its own prefixes to: transit providers, or peers at an exchange.
- AS1764NEXTLAYER Next Layer Telekommunikationsdienstleistungs Und Beratungs16
ASPA
No ASPA
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
- ASPA explainedWhy AS47132 should publish an ASPA object
- 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/47132Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/47132" | jq