AS201724 HCS HCS LIMITED
🇭🇰Org handle: ORG-HCSL3-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Routing hygiene
Score 86/100 · High riskRPKI ROA coverage
0%
3 prefixes RPKI invalid
IRR route objects
0%
3 prefixes registered for another origin
Hijack signals
1
1 announced against others' ROAs, 0 own announced by others
Upstreams
2
diversity 44/100
- 100% of announced prefixes (3 of 3) have no valid ROA, 3 of them RPKI invalid
- Announces 1 prefix that RPKI assigns to another network (possible hijack or misconfiguration)
- 100% of announced prefixes (3 of 3) have no IRR route object for this ASN
Based on 3 announced prefixes, updated daily (2026-10-24). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Invalid | - | 2026-10-26 | |
| Invalid | - | 2026-10-26 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 82.163.16.0/24 | 🇬🇧 GB | RIPE | assigned |
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 AS201724 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/201724Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/201724" | jq