AS48176 OOOSET-AS MTS PJSC
🇷🇺Org handle: ORG-ZM1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
34total
33 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)37,120
Announced (BGP)41,984
IPv6 Addresses
Allocated (RIR)4.9×10²⁷
Announced (BGP)4.9×10²⁷
Announced Prefixes
(BGP)34|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | - | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
1-10 of 34
1 / 4
Allocated Prefixes
(RIR)30Prefix | Country | RIR | Status |
|---|---|---|---|
| 37.18.152.0/21 | 🇷🇺 RU | RIPENCC | allocated |
| 62.122.240.0/21 | 🇷🇺 RU | RIPENCC | assigned |
| 81.177.56.0/21 | 🇷🇺 RU | RIPENCC | allocated |
| 81.177.60.0/22 | 🇷🇺 RU | RIPE | assigned |
| 81.177.184.0/24 | 🇷🇺 RU | RIPE | assigned |
| 81.177.187.0/24 | 🇷🇺 RU | RIPE | assigned |
| 81.177.188.0/22 | 🇷🇺 RU | RIPE | assigned |
| 81.177.195.0/24 | 🇷🇺 RU | RIPE | assigned |
| 81.177.198.0/23 | 🇷🇺 RU | RIPE | assigned |
| 81.177.200.0/21 | 🇷🇺 RU | RIPE | assigned |
1-10 of 30
1 / 3
All 34 announced prefixes of AS48176 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS48176 hands its own prefixes to: transit providers, or peers at an exchange.
- AS8359MTS PJSC34
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 AS48176 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/48176Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/48176" | jq