AS198624 Hexado Petr Balek trading as Hexado.pro
🇨🇿Org handle: ORG-HA1253-RIPE
Hexado.pro
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)3.1×10²⁶
Routing hygiene
Score 39/100 · Medium riskRPKI ROA coverage
50%
2 prefixes RPKI invalid
IRR route objects
75%
1 prefix registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
2
diversity 50/100
- 50% of announced prefixes (2 of 4) have no valid ROA, 2 of them RPKI invalid
- 1 prefix registered in IRR route objects for another active network and not authorized by a ROA
- 25% of announced prefixes (1 of 4) have no IRR route object for this ASN
Based on 4 announced prefixes, updated daily (2026-10-17). How the score works · RPKI explained
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
87.76.158.0/24MOAS | No ROA | - | 2026-10-19 |
87.232.124.0/24MOAS | Invalid | - | 2026-10-19 |
| Valid | RIPE | 2026-10-19 | |
| Invalid | RIPE | 2026-10-19 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 87.232.124.0/24 | 🇨🇿 CZ | RIPE | assigned |
| 2a06:9801:26e::/48 | 🇨🇿 CZ | RIPE | assigned |
| 2a14:7583:ea00::/40 | 🇨🇿 CZ | RIPE | assigned |
ASPA
No ASPA
Abuse Contact
+31205354444
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 AS198624 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/198624Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/198624" | jq