AS56367 ALUE-NET ALUE LTD
🇬🇧Org handle: ORG-AL1008-RIPE
ALUE NETWORK
RIPE NCCallocated
Announced Prefixes (BGP)
2total
0 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)2.4×10²⁴
Announced (BGP)2.4×10²⁴
Routing hygiene
Score 5/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
2
diversity 50/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 2 announced prefixes, updated daily (2026-10-23). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a0f:1cc5:4010::/48 | 🇭🇰 HK | RIPE | assigned |
| 2a0f:1cc5:4014::/48 | 🇯🇵 JP | RIPE | assigned |
All 2 announced prefixes of AS56367 →
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 AS56367 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/56367Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/56367" | jq