AS50071 SRDV-AS MTS PJSC
🇷🇺Org handle: ORG-ZM1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
4 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)6,656
Announced (BGP)7,168
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | - | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 37.72.80.0/20 | 🇷🇺 RU | RIPE | assigned |
| 77.93.110.0/23 | 🇷🇺 RU | RIPE | assigned |
| 77.93.112.0/21 | 🇷🇺 RU | RIPE | assigned |
All 4 announced prefixes of AS50071 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS50071 hands its own prefixes to: transit providers, or peers at an exchange.
- AS8359MTS PJSC4
ASPA
No ASPA
Abuse Contact
+31205354444
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 AS50071 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/50071Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/50071" | jq