AS34372 vegasystems-as VegaSystems GmbH & Co. KG
๐ฉ๐ชOrg handle: ORG-AFG1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
8total
6 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)6,656
Announced (BGP)5,632
IPv6 Addresses
Allocated (RIR)8.4ร10ยฒโธ
Announced (BGP)4.9ร10ยฒโท
Prefix Limit (IPv4)
20
Prefix Limit (IPv6)
10
Country
๐ฉ๐ช DERIR
RIPE NCCStatus
allocated
Allocated
2004-12-28
Announced Prefixes
(BGP)8|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)13Prefix | Country | RIR | Status |
|---|---|---|---|
| 80.70.176.0/20 | ๐ฉ๐ช DE | RIPENCC | allocated |
| 80.70.176.128/25 | ๐ฉ๐ช DE | RIPE | assigned |
| 80.70.180.224/27 | ๐ฉ๐ช DE | RIPE | assigned |
| 80.70.181.64/26 | ๐ฉ๐ช DE | RIPE | assigned |
| 80.70.190.0/27 | ๐ฉ๐ช DE | RIPE | assigned |
| 80.70.191.0/24 | ๐ฉ๐ช DE | RIPE | assigned |
| 91.208.58.0/24 | ๐ฉ๐ช DE | RIPENCC | assigned |
| 185.192.76.0/22 | ๐ฉ๐ช DE | RIPENCC | allocated |
| 185.192.76.0/24 | ๐ฉ๐ช DE | RIPE | assigned |
| 185.192.78.0/23 | ๐ฉ๐ช DE | RIPE | assigned |
1-10 of 13
1 / 2
All 8 announced prefixes of AS34372 โ
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS34372 hands its own prefixes to: transit providers, or peers at an exchange.
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 AS34372 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/34372Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/34372" | jq