AS60539 Huicast_Telecom Huicast Telecom Limited
ππ°Org handle: ORG-HTL24-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2,060total
4 IPv42,056 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)2,048
IPv6 Addresses
Allocated (RIR)6.3Γ10Β²βΉ
Announced (BGP)1.2Γ10Β³β°
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
10,000
Country
ππ° HKRIR
RIPE NCCStatus
allocated
Allocated
2023-08-14
Routing hygiene
Score 35/100 Β· Medium riskRPKI ROA coverage
12.9%
17 prefixes RPKI invalid
IRR route objects
99.1%
19 prefixes registered for another origin
Hijack signals
1
1 announced against others' ROAs, 0 own announced by others
Upstreams
4
diversity 68/100
- 87% of announced prefixes (1795 of 2060) have no valid ROA, 17 of them RPKI invalid
- Announces 1 prefix that RPKI assigns to another network (possible hijack or misconfiguration)
Based on 2,060 announced prefixes, updated daily (2026-10-27). How the score works Β· RPKI explained
Announced Prefixes
(BGP)1,000 of 2,060|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | Other IRRRIPE | - | |
23.172.216.0/24MOAS | Valid | ARIN | - |
130.12.44.0/22MOAS | Invalid | - | - |
161.248.28.0/23MOAS | No ROA | - | - |
2401:e3a0:1::/48MOAS | No ROA | - | - |
2602:f959::/40MOAS | Valid | ARIN | - |
| No ROA | RIPE | - | |
| No ROA | - | - | |
| No ROA | - | - | |
| No ROA | - | - |
1-10 of 1,000
1 / 100
Allocated Prefixes
(RIR)12Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a13:aac0::/29 | ππ° HK | RIPENCC | allocated |
| 2a13:aac7:60::/44 | πΊπ¦ UA | RIPE | assigned |
| 2a13:aac7:100::/40 | πΉπ― TJ | RIPE | assigned |
| 2a13:aac7:100::/46 | π³π± NL | RIPE | assigned |
| 2a13:aac7:200::/40 | πΊπΏ UZ | RIPE | assigned |
| 2a13:aac7:300::/40 | πΈπ¬ SG | RIPE | assigned |
| 2a13:aac7:400::/40 | ππ° HK | RIPE | assigned |
| 2a13:aac7:500::/40 | π¨π CH | RIPE | assigned |
| 2a13:aac7:600::/40 | π¨π¦ CA | RIPE | assigned |
| 2a13:aac7:700::/40 | πΊπΈ US | RIPE | assigned |
1-10 of 12
1 / 2
All 2,060 announced prefixes of AS60539 β
BGP Neighbours
(seen in AS paths)Upstreams (4)
Networks AS60539 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (11)
Networks whose own prefixes AS60539 passes on: usually its customers.
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 AS60539 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/60539Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/60539" | jq