AS39422 SKM-AS Oleksandr Yaremenko
🇺🇦Org handle: ORG-SCN2-RIPE
SKM Network
RIPE NCCallocated
Announced Prefixes (BGP)
14total
14 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)2,560
Announced (BGP)7,680
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)14|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 |
1-10 of 14
1 / 2
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 176.108.232.0/21 | 🇺🇦 UA | RIPENCC | assigned |
| 195.182.202.0/23 | 🇺🇦 UA | RIPENCC | assigned |
All 14 announced prefixes of AS39422 →
BGP Neighbours
(seen in AS paths)Upstreams (6)
Networks AS39422 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (3)
Networks whose own prefixes AS39422 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS39422 in the transit part of AS paths: peers, providers or customers.
- AS35297DATALINE5
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 AS39422 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/39422Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/39422" | jq