AS203923 HOYOVERSE-AS HOYOVERSE NETWORK LTD
π¬π§Org handle: ORG-HNL24-RIPE
ip geolocation: https://mhyidc.com/HOYOVERSE-NETWORK-LTD-geo-feed.csv
RIPE NCCallocated
Announced Prefixes (BGP)
15total
3 IPv412 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)768
IPv6 Addresses
Allocated (RIR)3.2Γ10Β²βΆ
Announced (BGP)1.4Γ10Β²β΅
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
50
Country
π¬π§ GBRIR
RIPE NCCStatus
allocated
Allocated
2025-11-10
Routing hygiene
Score 8/100 Β· Low riskRPKI ROA coverage
93.3%
no RPKI invalid prefixes
IRR route objects
93.3%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
5
diversity 52/100
- 7% of announced prefixes (1 of 15) have no valid ROA
Based on 15 announced prefixes, updated daily (2026-10-26). How the score works Β· RPKI explained
Announced Prefixes
(BGP)15|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
103.49.61.0/24MOAS | Valid | APNIC | 2026-10-26 |
| Valid | Other IRRRIPE | 2026-10-26 | |
150.129.43.0/24MOAS | Valid | APNICOther IRR | 2026-10-26 |
| Valid | APNIC | 2026-10-26 | |
| Valid | APNIC | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | - | 2026-10-26 |
1-10 of 15
1 / 2
Allocated Prefixes
(RIR)13Prefix | Country | RIR | Status |
|---|---|---|---|
| 2406:840:9661::/48 | πΈπ¬ SG | APNIC | assigned |
| 2406:840:9666::/48 | π²π΄ MO | APNIC | assigned |
| 2a0f:1cc5:400::/40 | π¬π§ GB | RIPE | assigned |
| 2a0f:1cc5:401::/48 | ππ° HK | RIPE | assigned |
| 2a0f:1cc5:402::/48 | π²π΄ MO | RIPE | assigned |
| 2a0f:1cc5:403::/48 | π―π΅ JP | RIPE | assigned |
| 2a0f:1cc5:404::/48 | πΉπΌ TW | RIPE | assigned |
| 2a0f:1cc5:405::/48 | π¬π§ GB | RIPE | assigned |
| 2a0f:1cc5:406::/48 | π²πΎ MY | RIPE | assigned |
| 2a0f:1cc5:407::/48 | ππ° HK | RIPE | assigned |
1-10 of 13
1 / 2
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 AS203923 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/203923Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/203923" | jq