AS50916 NADYMSS-AS Yan Telecom Ltd
🇷🇺Org handle: ORG-YTL13-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
6total
6 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)3,328
Announced (BGP)3,328
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | - | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | - | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 |
Allocated Prefixes
(RIR)6Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.221.48.0/23 | 🇷🇺 RU | RIPENCC | assigned |
| 91.238.222.0/23 | 🇷🇺 RU | RIPENCC | assigned |
| 93.170.124.0/22 | 🇷🇺 RU | RIPE | assigned |
| 195.191.220.0/23 | 🇷🇺 RU | RIPENCC | assigned |
| 195.242.216.0/23 | 🇷🇺 RU | RIPENCC | assigned |
| 195.242.216.0/24 | 🇷🇺 RU | RIPENCC | assigned |
All 6 announced prefixes of AS50916 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS50916 hands its own prefixes to: transit providers, or peers at an exchange.
- AS31133MF MGSM PJSC MegaFon6
Transfer History
Registry transfers of AS50916 between organisations.
- AS50916Transfer ·
- AS50916Transfer ·
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 AS50916 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/50916Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/50916" | jq