AS39798 MivoCloud MivoCloud SRL
🇲🇩Org handle: ORG-MS569-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
30total
19 IPv411 IPv6
IPv4 Addresses
Allocated (RIR)10,240
Announced (BGP)6,400
IPv6 Addresses
Allocated (RIR)7.9×10²⁹
Announced (BGP)1.5×10²⁹
Listed on the threat map (2026-10-11)
Large hosting providers appear because attackers rent their servers, not necessarily because of the operator.
Announced Prefixes
(BGP)30|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | Other IRRRIPE | - | |
| Valid | RIPE | - | |
| Valid | Other IRRRIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | Other IRRRIPE | - | |
| Valid | RIPE | - |
1-10 of 30
1 / 3
Allocated Prefixes
(RIR)36Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.181.156.0/22 | 🇲🇩 MD | RIPENCC | allocated |
| 5.181.156.0/24 | 🇲🇩 MD | RIPE | assigned |
| 5.181.157.0/24 | 🇲🇩 MD | RIPE | assigned |
| 5.181.158.0/24 | 🇲🇩 MD | RIPE | assigned |
| 5.181.159.0/24 | 🇺🇸 US | RIPE | assigned |
| 5.252.176.0/22 | 🇲🇩 MD | RIPENCC | allocated |
| 5.252.176.0/24 | 🇷🇺 RU | RIPE | assigned |
| 5.252.177.0/24 | 🇺🇸 US | RIPE | assigned |
| 5.252.178.0/24 | 🇷🇴 RO | RIPE | assigned |
| 5.252.179.0/24 | 🇩🇪 DE | RIPE | assigned |
1-10 of 36
1 / 4
All 30 announced prefixes of AS39798 →
BGP Neighbours
(seen in AS paths)Upstreams (7)
Networks AS39798 hands its own prefixes to: transit providers, or peers at an exchange.
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 AS39798 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/39798Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/39798" | jq