AS21367 WILAND-AS TrunkMobile JSC
π·πΊOrg handle: ORG-TJ113-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
13total
11 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)27,648
Announced (BGP)27,648
IPv6 Addresses
Allocated (RIR)1.5Γ10Β²βΉ
Announced (BGP)1.5Γ10Β²βΉ
Prefix Limit (IPv4)
50
Prefix Limit (IPv6)
10
Country
π·πΊ RURIR
RIPE NCCStatus
allocated
Allocated
2011-06-15
Announced Prefixes
(BGP)13|
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 | 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 | |
| No ROA | RIPE | 2026-10-11 |
1-10 of 13
1 / 2
Allocated Prefixes
(RIR)13Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.134.216.0/21 | π·πΊ RU | RIPENCC | allocated |
| 31.22.32.0/21 | π·πΊ RU | RIPENCC | allocated |
| 46.148.192.0/20 | π·πΊ RU | RIPENCC | assigned |
| 77.246.224.0/20 | π·πΊ RU | RIPENCC | allocated |
| 80.250.208.0/20 | π·πΊ RU | RIPENCC | allocated |
| 84.39.128.0/21 | π·πΊ RU | RIPENCC | allocated |
| 95.143.112.0/20 | π·πΊ RU | RIPENCC | allocated |
| 176.74.8.0/21 | π·πΊ RU | RIPENCC | allocated |
| 185.36.156.0/22 | π·πΊ RU | RIPENCC | allocated |
| 185.245.148.0/22 | π·πΊ RU | RIPENCC | allocated |
1-10 of 13
1 / 2
All 13 announced prefixes of AS21367 β
BGP Neighbours
(seen in AS paths)Upstreams (4)
Networks AS21367 hands its own prefixes to: transit providers, or peers at an exchange.
Transfer History
Registry transfers of AS21367 between organisations.
- AS21367Transfer Β·
- AS21367Transfer Β·
| Date | Resource | From | To | Type |
|---|---|---|---|---|
| AS21367 | Wiland Ltd | TrunkMobile JSC | Transfer | |
| AS21367 | Zvezda Telecom Ltd. | Wiland Ltd | Transfer |
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 AS21367 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/21367Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/21367" | jq