AS39799 COMINTEL-AS MTS PJSC
🇷🇺Org handle: ORG-ZM1-RIPE
Tyumen, Russia
RIPE NCCallocated
Announced Prefixes (BGP)
5total
5 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)7,680
Announced (BGP)7,680
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
🇷🇺 RURIR
RIPE NCCStatus
allocated
Allocated
2007-05-04
Announced Prefixes
(BGP)5|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| 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 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 77.239.192.0/23 | 🇷🇺 RU | RIPE | assigned |
| 77.239.196.0/22 | 🇷🇺 RU | RIPE | assigned |
| 109.198.72.0/21 | 🇷🇺 RU | RIPE | assigned |
| 109.198.80.0/21 | 🇷🇺 RU | RIPE | assigned |
| 109.198.88.0/21 | 🇷🇺 RU | RIPE | assigned |
All 5 announced prefixes of AS39799 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS39799 hands its own prefixes to: transit providers, or peers at an exchange.
- AS41822TNGS NORTH MTS PJSC5
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 AS39799 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/39799Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/39799" | jq