AS15672 TZTELECOM OOO Telecom TZ
🇷🇺Org handle: ORG-TT4-RIPE
advertise with no-export community (not available in all areas) x=7
RIPE NCCallocated
Announced Prefixes (BGP)
83total
82 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)33,536
Announced (BGP)35,328
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)83|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
31.24.255.0/24MOAS | Invalid | - | - |
| No ROA | RIPE | - | |
| No ROA | RIPE | - | |
| No ROA | RIPE | - | |
| No ROA | RIPE | - | |
| No ROA | RIPE | - | |
| No ROA | RIPE | - | |
| No ROA | RIPE | - | |
| No ROA | RIPE | - | |
| No ROA | RIPE | - |
1-10 of 83
1 / 9
Allocated Prefixes
(RIR)35Prefix | Country | RIR | Status |
|---|---|---|---|
| 31.24.255.0/24 | 🇭🇰 HK | RIPENCC | allocated |
| 85.31.112.0/21 | 🇷🇺 RU | RIPENCC | allocated |
| 85.31.112.0/24 | 🇷🇺 RU | RIPE | assigned |
| 85.31.113.0/24 | 🇷🇺 RU | RIPE | assigned |
| 85.31.114.0/24 | 🇷🇺 RU | RIPE | assigned |
| 85.31.115.0/24 | 🇷🇺 RU | RIPE | assigned |
| 85.31.116.0/24 | 🇷🇺 RU | RIPE | assigned |
| 85.90.96.0/19 | 🇷🇺 RU | RIPENCC | allocated |
| 85.90.96.0/22 | 🇷🇺 RU | RIPE | assigned |
| 85.90.96.0/24 | 🇷🇺 RU | RIPE | assigned |
1-10 of 35
1 / 4
All 83 announced prefixes of AS15672 →
BGP Neighbours
(seen in AS paths)Upstreams (4)
Networks AS15672 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (5)
Networks whose own prefixes AS15672 passes on: usually its customers.
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 AS15672 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/15672Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/15672" | jq