AS5378 Vodafone Limited
🇬🇧Org handle: ORG-VL225-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
24total
23 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1.5M
Announced (BGP)2.8M
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Prefix Limit (IPv4)
2,000
Prefix Limit (IPv6)
5
Country
🇬🇧 GBRIR
RIPE NCCStatus
allocated
Allocated
1995-06-08
Announced Prefixes
(BGP)24|
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 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
1-10 of 24
1 / 3
Allocated Prefixes
(RIR)10Prefix | Country | RIR | Status |
|---|---|---|---|
| 62.49.0.0/16 | 🇬🇧 GB | RIPENCC | allocated |
| 62.56.0.0/17 | 🇬🇧 GB | RIPENCC | allocated |
| 80.176.0.0/15 | 🇬🇧 GB | RIPENCC | allocated |
| 81.76.0.0/14 | 🇬🇧 GB | RIPENCC | allocated |
| 83.104.0.0/14 | 🇬🇧 GB | RIPENCC | allocated |
| 84.64.0.0/13 | 🇬🇧 GB | RIPENCC | allocated |
| 90.255.254.0/24 | 🇬🇧 GB | RIPE | assigned |
| 193.237.0.0/16 | 🇬🇧 GB | RIPENCC | allocated |
| 212.228.0.0/15 | 🇬🇧 GB | RIPE | assigned |
| 2a0a:ef40::/29 | 🇬🇧 GB | RIPENCC | allocated |
All 24 announced prefixes of AS5378 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS5378 hands its own prefixes to: transit providers, or peers at an exchange.
- AS1273CW Vodafone Group PLC24
Downstreams (2)
Networks whose own prefixes AS5378 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS5378 in the transit part of AS paths: peers, providers or customers.
- AS37468ANGOLA CABLES1
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 AS5378 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/5378Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/5378" | jq