AS209178 IPv4Superhub IPv4 Superhub Limited
🇭🇰Org handle: ORG-ISL74-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 43/100 · Medium riskRPKI ROA coverage
50%
1 prefix RPKI invalid
IRR route objects
50%
1 prefix registered for another origin
Hijack signals
2
0 announced against others' ROAs, 2 own announced by others
Upstreams
1
diversity 0/100
- 50% of announced prefixes (1 of 2) have no valid ROA, 1 of them RPKI invalid
- Only one upstream seen in the AS paths of its routes
- 50% of announced prefixes (1 of 2) have no IRR route object for this ASN
- 2 prefixes of this ASN announced by another network against its ROAs
Based on 2 announced prefixes, updated daily (2026-10-25). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
185.233.19.0/24MOAS | Valid | RIPE | 2026-10-25 |
| Invalid | - | 2026-10-25 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.233.19.0/24 | 🇭🇰 HK | RIPE | assigned |
All 2 announced prefixes of AS209178 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS209178 hands its own prefixes to: transit providers, or peers at an exchange.
- AS214743COGENTO Backbone Limited2
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 AS209178 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/209178Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/209178" | jq