AS48004 KCT-AS PE Tsibrankov Konstantin Igorevich
🇺🇦Org handle: ORG-KT18-RIPE
***KCT-AS***
RIPE NCCallocated
Announced Prefixes (BGP)
4total
4 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)3,328
Announced (BGP)3,328
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)4|
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 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.205.157.0/24 | 🇬🇪 GE | RIPENCC | allocated |
| 91.205.216.0/22 | 🇺🇦 UA | RIPENCC | assigned |
| 193.107.112.0/22 | 🇺🇦 UA | RIPENCC | assigned |
| 195.18.16.0/22 | 🇺🇦 UA | RIPENCC | assigned |
All 4 announced prefixes of AS48004 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS48004 hands its own prefixes to: transit providers, or peers at an exchange.
- AS48084UMLC Uzhnie Magistraljnie Linii Svyazi4
Downstreams (4)
Networks whose own prefixes AS48004 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS48004 in the transit part of AS paths: peers, providers or customers.
- AS6789CRELCOM NET CRELCOM9
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 AS48004 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/48004Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/48004" | jq