AS201746 OLIVENET-AS Olivenet Network S.L.
🇪🇸Org handle: ORG-ETS6-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
79total
79 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)10,752
Announced (BGP)37,888
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)0
Announced Prefixes
(BGP)79|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
37.0.107.0/24MOAS | Valid | RIPE | - |
37.26.252.0/22MOAS | Valid | RIPE | - |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - |
1-10 of 79
1 / 8
Allocated Prefixes
(RIR)22Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.94.100.0/24 | 🇪🇸 ES | RIPE | assigned |
| 45.131.29.0/25 | 🇪🇸 ES | RIPE | assigned |
| 45.131.29.128/25 | 🇪🇸 ES | RIPE | assigned |
| 46.8.160.0/20 | 🇨🇿 CZ | RIPENCC | allocated |
| 94.158.253.0/24 | 🇪🇸 ES | RIPE | assigned |
| 178.236.125.0/24 | 🇪🇸 ES | RIPENCC | allocated |
| 185.6.32.0/23 | 🇪🇸 ES | RIPE | assigned |
| 185.6.34.0/23 | 🇪🇸 ES | RIPE | assigned |
| 185.49.168.0/22 | 🇪🇸 ES | RIPENCC | allocated |
| 185.49.168.0/24 | 🇪🇸 ES | RIPE | assigned |
1-10 of 22
1 / 3
All 79 announced prefixes of AS201746 →
BGP Neighbours
(seen in AS paths)Upstreams (5)
Networks AS201746 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (11)
Networks whose own prefixes AS201746 passes on: usually its customers.
- AS50564ELECTRONICAMARTINEZ CARTAGO TELECOM S. L36
- AS211261FIBRANET Tecnologia Y Sistemas SL36
- AS51151COMENERSOL Comunicaciones Enersol, S.L24
- AS199290MOWITEL INSTALACIONES Y SERVICIOS MOWITEL S.L17
- AS213686AION QTAL ON FIBRA OPTICA AION QTAL ON FIBRA OPTICA S.L15
- AS43160ES TEMPLUS SPAIN TEMPLUS SPAIN SL11
- AS57074Waytel Fibra SL Waytel Fibra SL11
- AS49173ASN TELECABLE Almonte, S.L9
- AS206853Nolu NETWORK S.L8
- AS215714Codipro CONTROL DIGITAL DE PROCESOS SL7
- AS204817AS1 NETCAN Technologies, S.L2
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 AS201746 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/201746Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/201746" | jq