AS202872 KMENET KME, spol. s r. o.
🇨🇿Org handle: ORG-KSSR2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.149.128.0/23 | 🇨🇿 CZ | RIPE | assigned |
| 185.149.130.0/23 | 🇨🇿 CZ | RIPE | assigned |
| 2a07:6880::/32 | 🇨🇿 CZ | RIPE | assigned |
All 3 announced prefixes of AS202872 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS202872 hands its own prefixes to: transit providers, or peers at an exchange.
- AS197451VUTBR Brno University Of Technology3
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 AS202872 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/202872Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/202872" | jq