AS214962 ByteSphere Goh Jing Ming
🇲🇾Org handle: ORG-BA1639-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
1 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)3.1×10²⁶
Announced (BGP)2.4×10²⁴
Routing hygiene
Score 61/100 · High riskRPKI ROA coverage
66.7%
1 prefix RPKI invalid
IRR route objects
66.7%
1 prefix registered for another origin
Hijack signals
2
1 announced against others' ROAs, 1 own announced by others
Upstreams
2
diversity 44/100
- Announces 1 prefix that RPKI assigns to another network (possible hijack or misconfiguration)
- 33% of announced prefixes (1 of 3) have no valid ROA, 1 of them RPKI invalid
- 33% of announced prefixes (1 of 3) have no IRR route object for this ASN
- 1 prefix of this ASN announced by another network against its ROAs
Based on 3 announced prefixes, updated daily (2026-10-23). How the score works · RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
109.176.83.0/24MOAS | Invalid | - | 2026-10-27 |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 109.176.83.0/24 | 🇪🇺 EU | RIPE | assigned |
| 2a13:a5c7:2000::/40 | 🇲🇾 MY | RIPE | assigned |
| 2a13:a5c7:2000::/48 | 🇲🇾 MY | RIPE | assigned |
| 2a13:a5c7:2003::/48 | 🇻🇦 VA | 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 AS214962 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/214962Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/214962" | jq