AS41722 MIRAN-AS Miran Ltd.
🇷🇺Org handle: ORG-ML60-RIPE
Miran DC
RIPE NCCallocated
Announced Prefixes (BGP)
51total
42 IPv49 IPv6
IPv4 Addresses
Allocated (RIR)10,752
Announced (BGP)10,752
IPv6 Addresses
Allocated (RIR)1.5×10²⁹
Announced (BGP)1.5×10²⁹
Prefix Limit (IPv4)
100
Prefix Limit (IPv6)
50
Country
🇷🇺 RURIR
RIPE NCCStatus
allocated
Allocated
2006-10-13
Announced Prefixes
(BGP)51|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 |
1-10 of 51
1 / 6
Allocated Prefixes
(RIR)44Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.142.80.0/24 | 🇷🇺 RU | RIPE | assigned |
| 91.142.81.0/24 | 🇷🇺 RU | RIPE | assigned |
| 91.142.82.0/24 | 🇷🇺 RU | RIPE | assigned |
| 91.142.83.0/24 | 🇷🇺 RU | RIPE | assigned |
| 91.142.84.0/24 | 🇷🇺 RU | RIPE | assigned |
| 91.142.85.0/24 | 🇷🇺 RU | RIPE | assigned |
| 91.142.86.0/24 | 🇷🇺 RU | RIPE | assigned |
| 91.142.88.0/24 | 🇷🇺 RU | RIPE | assigned |
| 91.142.89.0/24 | 🇷🇺 RU | RIPE | assigned |
| 91.142.90.0/24 | 🇷🇺 RU | RIPE | assigned |
1-10 of 44
1 / 5
All 51 announced prefixes of AS41722 →
BGP Neighbours
(seen in AS paths)Upstreams (4)
Networks AS41722 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (9)
Networks whose own prefixes AS41722 passes on: usually its customers.
- AS205864Edisoft Ediweb4
- AS212165Kvmka Alex Group4
- AS12654RIPE NCC RIS Reseaux IP Europeens Network Coordination Centre (RIPE NCC)2
- AS201738UFO TECHNOLOGIES LIMITED UFO TECHNOLOGIES LIMITED2
- AS43951GT LT "Lanit Tercom"1
- AS57596ITH1
- AS202989Ofis24 OOO1
- AS214367RU PAYGINE JSC "Pay Engine"1
- AS218988RDPTERM Lisitsina Elena Yurievna1
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 AS41722 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/41722Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/41722" | jq