AS212371 HUIGU-AS Huizhou HuiGu CloudTech Co., Ltd.
🇨🇳Org handle: ORG-HHCC1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
3 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)768
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)0
Routing hygiene
Score 65/100 · High riskRPKI ROA coverage
0%
no RPKI invalid prefixes
IRR route objects
0%
1 prefix registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- 100% of announced prefixes (3 of 3) have no valid ROA
- 100% of announced prefixes (3 of 3) have no IRR route object for this ASN
- 1 prefix registered in IRR route objects for another active network and not authorized by a ROA
- Only one upstream seen in the AS paths of its routes
Based on 3 announced prefixes, updated daily (2026-10-12). How the score works · RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | - | 2026-10-12 | |
| No ROA | - | 2026-10-12 | |
| No ROA | - | 2026-10-12 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a0e:aa07:e047::/48 | 🇬🇧 GB | RIPE | assigned |
All 3 announced prefixes of AS212371 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS212371 hands its own prefixes to: transit providers, or peers at an exchange.
- AS7195EDGEUNO S.A.S3
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 AS212371 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/212371Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/212371" | jq