AS35728 MTS-PENZA-AS MTS PJSC
🇷🇺Org handle: ORG-ZM1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
6total
6 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)65,536
Announced (BGP)66,560
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 77.108.192.0/18 | 🇷🇺 RU | RIPENCC | allocated |
| 82.209.64.0/18 | 🇷🇺 RU | RIPENCC | allocated |
| 85.234.32.0/19 | 🇷🇺 RU | RIPENCC | allocated |
| 92.246.160.0/19 | 🇷🇺 RU | RIPENCC | allocated |
| 95.83.64.0/18 | 🇷🇺 RU | RIPENCC | allocated |
All 6 announced prefixes of AS35728 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS35728 hands its own prefixes to: transit providers, or peers at an exchange.
- AS8359MTS PJSC6
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 AS35728 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/35728Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/35728" | jq