AS50174 INTEXCOM-AS Intexcom OOO
🇷🇺Org handle: ORG-IO32-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
16total
16 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,280
Announced (BGP)7,168
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)16|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-09 | |
| No ROA | RIPE | 2026-10-09 | |
| No ROA | RIPE | 2026-10-09 | |
| No ROA | RIPE | 2026-10-09 | |
| No ROA | RIPE | 2026-10-09 | |
| No ROA | RIPE | 2026-10-09 | |
| No ROA | RIPE | 2026-10-09 | |
| No ROA | RIPE | 2026-10-09 | |
| No ROA | RIPE | 2026-10-09 | |
| No ROA | RIPE | 2026-10-09 |
1-10 of 16
1 / 2
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.229.100.0/24 | 🇷🇺 RU | RIPENCC | assigned |
| 193.106.4.0/22 | 🇷🇺 RU | RIPENCC | assigned |
All 16 announced prefixes of AS50174 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS50174 hands its own prefixes to: transit providers, or peers at an exchange.
- AS31133MF MGSM PJSC MegaFon16
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 AS50174 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/50174Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/50174" | jq