AS8580 SANDY MTS PJSC
🇷🇺Org handle: ORG-ZM1-RIPE
MTS Nizhniy Novgorod, Russia
RIPE NCCallocated
Announced Prefixes (BGP)
23total
23 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)2,816
Announced (BGP)55,040
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)23|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | - | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | - | 2026-10-11 | |
| No ROA | - | 2026-10-11 | |
| No ROA | - | 2026-10-11 | |
| No ROA | - | 2026-10-11 | |
| No ROA | - | 2026-10-11 | |
| No ROA | - | 2026-10-11 | |
| No ROA | - | 2026-10-11 | |
| No ROA | - | 2026-10-11 |
1-10 of 23
1 / 3
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 194.190.177.0/24 | 🇷🇺 RU | RIPE | assigned |
| 194.190.180.0/22 | 🇷🇺 RU | RIPE | assigned |
| 194.190.184.0/22 | 🇷🇺 RU | RIPE | assigned |
| 194.190.188.0/23 | 🇷🇺 RU | RIPE | assigned |
All 23 announced prefixes of AS8580 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS8580 hands its own prefixes to: transit providers, or peers at an exchange.
- AS8359MTS PJSC23
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 AS8580 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/8580Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/8580" | jq