AS8779 INFOCOM-KM KhmelnitskInfocom LTD
🇺🇦Org handle: ORG-KL33-RIPE
Khmelnitsky, Ukraine
RIPE NCCallocated
Announced Prefixes (BGP)
5total
4 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)16,896
Announced (BGP)16,896
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)5|
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 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 46.252.208.0/20 | 🇺🇦 UA | RIPENCC | allocated |
| 78.152.160.0/19 | 🇺🇦 UA | RIPENCC | allocated |
| 94.230.192.0/20 | 🇺🇦 UA | RIPENCC | allocated |
| 185.15.4.0/23 | 🇺🇦 UA | RIPE | assigned |
| 2a00:6740::/32 | 🇺🇦 UA | RIPENCC | allocated |
All 5 announced prefixes of AS8779 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS8779 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS8779 passes on: usually its customers.
- AS29663SNU Olga Soroka4
ASPA
No ASPA
Abuse Contact
+31205354444
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 AS8779 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/8779Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/8779" | jq