AS13075 MEGALABS-AS PJSC MegaFon
🇷🇺Org handle: ORG-OM1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
5total
4 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)1.2×10²⁴
Announced Prefixes
(BGP)5|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 83.149.13.0/24 | 🇷🇺 RU | RIPE | assigned |
| 83.149.14.0/24 | 🇷🇺 RU | RIPE | assigned |
| 91.213.104.0/24 | 🇷🇺 RU | RIPENCC | assigned |
| 195.208.38.0/24 | 🇷🇺 RU | RIPE | assigned |
| 2a03:d000:9000::/48 | 🇷🇺 RU | RIPE | assigned |
All 5 announced prefixes of AS13075 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS13075 hands its own prefixes to: transit providers, or peers at an exchange.
- AS31133MF MGSM PJSC MegaFon5
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 AS13075 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/13075Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/13075" | jq