AS208486 IPARFIBRA IPARFIBRA SL
🇪🇸Org handle: ORG-IS540-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
7total
7 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,792
Announced (BGP)2,816
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)0
Announced Prefixes
(BGP)7|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.149.180.0/23 | 🇪🇸 ES | RIPE | assigned |
| 103.253.140.0/22 | 🇪🇸 ES | RIPENCC | allocated |
| 194.147.226.0/24 | 🇪🇸 ES | RIPENCC | allocated |
| 2a12:7ac0::/29 | 🇪🇸 ES | RIPENCC | allocated |
All 7 announced prefixes of AS208486 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS208486 hands its own prefixes to: transit providers, or peers at an exchange.
- AS3262SARENET SAREnet, S.A7
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 AS208486 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/208486Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/208486" | jq