AS58014 ZUTOM ZUTOM s.r.o.
🇸🇰Org handle: ORG-ZS45-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)2,048
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | - | 2026-10-10 | |
| No ROA | - | 2026-10-10 | |
| No ROA | - | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 92.240.251.0/24 | 🇸🇰 SK | RIPE | assigned |
| 185.201.236.0/22 | 🇸🇰 SK | RIPENCC | allocated |
| 185.201.236.0/23 | 🇸🇰 SK | RIPE | assigned |
| 185.201.239.0/24 | 🇸🇰 SK | RIPE | assigned |
| 2a0a:cbc0::/29 | 🇸🇰 SK | RIPENCC | allocated |
All 4 announced prefixes of AS58014 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS58014 hands its own prefixes to: transit providers, or peers at an exchange.
- AS42005LIGHTSTORM COMMUNICATIONS SRO SK LightStorm Services S.R.O5
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 AS58014 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/58014Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/58014" | jq