AS48524 INTERRA-AS INTERRA telecommunications group, Ltd.
🇷🇺Org handle: ORG-LA171-RIPE
at Pervouralsk (Bilimbay, Severka, Sredneuralsk), Revda (Degtyarsk), Kachkanar, Lesnoy (N.Tura), Polevskoy, Krasnoufimsk, Asbest cities of Sverdlovsk reg
RIPE NCCallocated
Announced Prefixes (BGP)
31total
30 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)101,120
Announced (BGP)66,560
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)31|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | - | 2026-10-10 | |
| No ROA | - | 2026-10-10 | |
| No ROA | - | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 |
1-10 of 31
1 / 4
Allocated Prefixes
(RIR)29Prefix | Country | RIR | Status |
|---|---|---|---|
| 31.28.96.0/19 | 🇷🇺 RU | RIPENCC | allocated |
| 31.28.96.0/21 | 🇷🇺 RU | RIPE | assigned |
| 31.28.104.0/21 | 🇷🇺 RU | RIPE | assigned |
| 31.28.112.0/22 | 🇷🇺 RU | RIPE | assigned |
| 31.28.116.0/22 | 🇷🇺 RU | RIPE | assigned |
| 31.28.124.0/22 | 🇷🇺 RU | RIPE | assigned |
| 37.1.128.0/20 | 🇷🇺 RU | RIPENCC | allocated |
| 37.1.128.0/21 | 🇷🇺 RU | RIPE | assigned |
| 37.1.136.0/21 | 🇷🇺 RU | RIPE | assigned |
| 37.131.192.0/19 | 🇷🇺 RU | RIPENCC | allocated |
1-10 of 29
1 / 3
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 AS48524 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/48524Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/48524" | jq