AS58024 DZINET-AS Isaev Kamil Magomedovich
🇷🇺Org handle: ORG-IKM3-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
4 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,536
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)0
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)6Prefix | Country | RIR | Status |
|---|---|---|---|
| 77.105.145.0/24 | 🇷🇺 RU | RIPENCC | allocated |
| 77.105.165.0/24 | 🇷🇺 RU | RIPENCC | allocated |
| 77.105.166.0/23 | 🇷🇺 RU | RIPENCC | allocated |
| 84.54.45.0/24 | 🇷🇺 RU | RIPENCC | allocated |
| 84.54.46.0/24 | 🇷🇺 RU | RIPENCC | allocated |
| 2a09:1280::/29 | 🇷🇺 RU | RIPENCC | allocated |
All 4 announced prefixes of AS58024 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS58024 hands its own prefixes to: transit providers, or peers at an exchange.
- AS42861FOTONTELECOM TRANSIT Foton Telecom CJSC4
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 AS58024 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/58024Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/58024" | jq