AS52091 LEVEL-MSK-AS Level-MSK Ltd.
🇷🇺Org handle: ORG-LL304-RIPE
Level-MSK Ltd.
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)768
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)1.5×10²⁹
Routing hygiene
Score 3/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
4
diversity 75/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 4 announced prefixes, updated daily (2026-10-24). How the score works · RPKI explained
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-24 | |
| Valid | RIPE | 2026-10-24 | |
| Valid | RIPE | 2026-10-24 | |
| Valid | RIPE | 2026-10-24 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 31.133.40.0/23 | 🇷🇺 RU | RIPE | assigned |
| 31.133.42.0/24 | 🇷🇺 RU | RIPE | assigned |
All 4 announced prefixes of AS52091 →
Upstream Providers(5)
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS47694 | 🇷🇺LEVEL-MSK-AS Level-MSK Ltd. |
BGP Neighbours
(seen in AS paths)Upstreams (4)
Networks AS52091 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (5)
Networks whose own prefixes AS52091 passes on: usually its customers.
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/52091Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/52091" | jq