AS38364 LTEL RM 1706,Block A,Ocean Express,No.66
Announced Prefixes (BGP)
27total
6 IPv421 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)3,584
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Prefix Limit (IPv4)
20
Prefix Limit (IPv6)
100
Allocated
-
Announced Prefixes
(BGP)27|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
121.58.156.0/23MOAS | Valid | - | 2026-10-11 |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
122.200.104.0/22MOAS | Valid | - | 2026-10-11 |
122.200.120.0/22MOAS | Valid | - | 2026-10-11 |
| Valid | APNIC | 2026-10-11 | |
| Invalid | - | 2026-10-11 | |
| Invalid | - | 2026-10-11 | |
| Invalid | - | 2026-10-11 |
1-10 of 27
1 / 3
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 2403:7580::/32 | 🇨🇳 CN | APNIC | allocated |
All 27 announced prefixes of AS38364 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS38364 hands its own prefixes to: transit providers, or peers at an exchange.
- AS56048CMNET BEIJING AP China Mobile Communicaitons Corporation27
ASPA
No ASPA
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 AS38364 should publish an ASPA object
- IPv4 transfer marketTransfers published by all five RIRs
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/38364Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/38364" | jq