AS201926 vkdata VK DATA ApS
🇩🇰Org handle: ORG-VDA31-RIPE
-----BEGIN TOKEN-----57246531ad533a2110f55fcc245009b13530a0225295e87a62c4cdcb9a6d81ecc9d4b833e03d9a59e86f8fbb5ab0f4a1f42573aadf25d6604e2ce144a97e82ee-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.106.119.0/24 | 🇩🇰 DK | RIPENCC | allocated |
All 1 announced prefix of AS201926 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS201926 hands its own prefixes to: transit providers, or peers at an exchange.
- AS16276OVH SAS1
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 AS201926 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/201926Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/201926" | jq