AS43576 KUMIR-AS LTD "KuMIR TELECOM"
🇺🇦Org handle: ORG-LT13-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1,536
Announced (BGP)1,536
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)1.2×10²⁴
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.197.144.0/22 | 🇺🇦 UA | RIPENCC | assigned |
| 185.239.184.0/24 | 🇺🇦 UA | RIPE | assigned |
| 217.147.162.0/24 | 🇺🇦 UA | RIPE | assigned |
| 2a0c:6580::/48 | 🇺🇦 UA | RIPE | assigned |
All 4 announced prefixes of AS43576 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS43576 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (4)
Networks whose own prefixes AS43576 passes on: usually its customers.
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 AS43576 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/43576Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/43576" | jq