AS205345 HORALNET HoralNET s.r.o.
🇨🇿Org handle: ORG-HS198-RIPE
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Routing hygiene
Score 10/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
Based on 2 announced prefixes, updated daily (2026-10-18). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.221.124.0/22 | 🇨🇿 CZ | RIPENCC | allocated |
| 2a0d:c000::/29 | 🇨🇿 CZ | RIPENCC | allocated |
All 2 announced prefixes of AS205345 →
Upstream Providers(1)
| ASN | Name |
|---|---|
| AS207187 | 🇨🇿TKRJASEK TKR Jasek, s.r.o. |
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS205345 hands its own prefixes to: transit providers, or peers at an exchange.
- AS207187TKRJASEK TKR Jasek, S.R.O2
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/205345Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/205345" | jq