AS213102 BKTV BKTV GmbH
🇦🇹Org handle: ORG-BG313-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,536
Announced (BGP)1,280
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)0
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-09 | |
| No ROA | RIPE | 2026-10-09 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 94.124.115.0/24 | 🇦🇹 AT | RIPENCC | allocated |
| 103.203.180.0/22 | 🇦🇹 AT | RIPENCC | allocated |
| 185.36.20.0/24 | 🇦🇹 AT | RIPENCC | allocated |
| 2a14:ef00::/29 | 🇦🇹 AT | RIPENCC | allocated |
All 2 announced prefixes of AS213102 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS213102 hands its own prefixes to: transit providers, or peers at an exchange.
- AS8437UTA Hutchison Drei Austria2
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 AS213102 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/213102Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/213102" | jq