AS203208 CTU_AS4_2 Czech Telecommunication Office
🇨🇿Org handle: ORG-CTO1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
5total
2 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)768
Announced (BGP)768
IPv6 Addresses
Allocated (RIR)5.5×10²⁹
Announced (BGP)5.5×10²⁹
Announced Prefixes
(BGP)5|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.68.212.0/23 | 🇨🇿 CZ | RIPE | assigned |
| 185.68.214.0/24 | 🇨🇿 CZ | RIPE | assigned |
| 2a05:1c40::/30 | 🇨🇿 CZ | RIPE | assigned |
| 2a05:1c44::/31 | 🇨🇿 CZ | RIPE | assigned |
| 2a05:1c46::/32 | 🇨🇿 CZ | RIPE | assigned |
All 5 announced prefixes of AS203208 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS203208 hands its own prefixes to: transit providers, or peers at an exchange.
- AS6855SK TELEKOM Slovak Telekom, A.S5
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 AS203208 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/203208Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/203208" | jq