AS25085 ALUE-NET ALUE LTD
🇬🇧Org handle: ORG-AL1008-RIPE
ALUE NETWORK
RIPE NCCallocated
Announced Prefixes (BGP)
11total
0 IPv411 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)1.5×10²⁵
Announced (BGP)1.3×10²⁵
Routing hygiene
Score 13/100 · Low riskRPKI ROA coverage
81.8%
2 prefixes RPKI invalid
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
6
diversity 78/100
- 18% of announced prefixes (2 of 11) have no valid ROA, 2 of them RPKI invalid
Based on 11 announced prefixes, updated daily (2026-10-24). How the score works · RPKI explained
Announced Prefixes
(BGP)11|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Invalid | RIPE | 2026-10-26 |
1-10 of 11
1 / 2
Allocated Prefixes
(RIR)13Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a0f:1cc5:4001::/48 | 🇬🇧 GB | RIPE | assigned |
| 2a0f:1cc5:4002::/48 | 🇯🇵 JP | RIPE | assigned |
| 2a0f:1cc5:4003::/48 | 🇭🇰 HK | RIPE | assigned |
| 2a0f:1cc5:4004::/48 | 🇯🇵 JP | RIPE | assigned |
| 2a0f:1cc5:4006::/48 | 🇭🇰 HK | RIPE | assigned |
| 2a0f:1cc5:4007::/48 | 🇺🇸 US | RIPE | assigned |
| 2a0f:1cc5:4008::/48 | 🇨🇭 CH | RIPE | assigned |
| 2a0f:1cc5:4009::/48 | 🇸🇬 SG | RIPE | assigned |
| 2a0f:1cc5:4012::/48 | 🇯🇵 JP | RIPE | assigned |
| 2a0f:1cc5:4015::/48 | 🇬🇧 GB | RIPE | assigned |
1-10 of 13
1 / 2
All 11 announced prefixes of AS25085 →
BGP Neighbours
(seen in AS paths)Upstreams (6)
Networks AS25085 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS25085 passes on: usually its customers.
- AS56367ALUE NET ALUE1
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 AS25085 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/25085Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/25085" | jq