AS205575 VEO-TV-Alameda Veo Telecomunicaciones SL
🇪🇸Org handle: ORG-VA33439-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
9total
9 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)3,072
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)9|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-08 | |
| Valid | RIPE | 2026-10-08 | |
| Valid | RIPE | 2026-10-08 | |
| Valid | RIPE | 2026-10-08 | |
| Valid | RIPE | 2026-10-08 | |
| Valid | - | 2026-10-08 | |
| Valid | - | 2026-10-08 | |
| Valid | - | 2026-10-08 | |
| Valid | - | 2026-10-08 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 2.152.212.0/22 | 🇪🇸 ES | RIPENCC | allocated |
All 9 announced prefixes of AS205575 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS205575 hands its own prefixes to: transit providers, or peers at an exchange.
- AS29119SERVIHOSTING AIRE NETWORKS DEL MEDITERRANEO SL UNIPERSONAL9
Transfer History
Registry transfers of AS205575 between organisations.
- AS205575Transfer ·
- AS205575Transfer ·
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 AS205575 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/205575Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/205575" | jq