AS31473 BEARINGPOINT-MANAGED-AS BearingPoint GmbH
🇦🇹Org handle: ORG-BG275-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)1.2×10²⁴
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 194.76.210.0/24 | 🇦🇹 AT | RIPENCC | assigned |
| 194.76.239.0/24 | 🇦🇹 AT | RIPENCC | assigned |
| 2001:67c:2328::/48 | 🇦🇹 AT | RIPENCC | assigned |
All 3 announced prefixes of AS31473 →
BGP Neighbours
(seen in AS paths)ASPA
No ASPA
Abuse Contact
+31205354444
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 AS31473 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/31473Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/31473" | jq