AS35486 CORDOBADATACENTER TIC NEXT INDUSTRIES S.L.
🇪🇸Org handle: ORG-SIAT2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
4 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)2,048
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)0
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.79.28.0/22 | 🇪🇸 ES | RIPENCC | allocated |
| 185.79.28.0/24 | 🇪🇸 ES | RIPE | assigned |
| 185.79.29.0/24 | 🇪🇸 ES | RIPE | assigned |
| 185.79.30.0/23 | 🇪🇸 ES | RIPE | assigned |
| 2a05:7080::/29 | 🇪🇸 ES | RIPENCC | allocated |
All 4 announced prefixes of AS35486 →
BGP Neighbours
(seen in AS paths)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 AS35486 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/35486Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/35486" | jq