2a14:7581:8000::/36 - HALOCLOUD NETWORK HaloCloud Network Limited (AS50385)
CIDR
2a14:7581:8000::/36
IP Version
IPv6
Addresses
4951.7Y
Mask
/36
Country
🇯🇵 Japan
City
Tokyo
RIR
RIPE
Status
assigned
Allocated
-
Announced BGP Routes
0 of 0 routesRPKI:
IRR:
Swipe sideways to see all columns →
| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| This prefix is not announced as a whole. Parts of it are announced as more-specific prefixes, see below. | ||||
More-Specific Announcements
8 more-specific announcements| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| 2a14:7581:8000::/40 | AS50385 HALOCLOUD-NETWORK HaloCloud Network Limited | Valid | - | 2026-10-26 |
| 2a14:7581:8100::/40 | AS50385 HALOCLOUD-NETWORK HaloCloud Network Limited | Valid | - | 2026-10-26 |
| 2a14:7581:8200::/39 | AS50385 HALOCLOUD-NETWORK HaloCloud Network Limited | Valid | - | 2026-10-26 |
| 2a14:7581:8400::/39 | AS50385 HALOCLOUD-NETWORK HaloCloud Network Limited | Valid | - | 2026-10-26 |
| 2a14:7581:8600::/39 | AS50385 HALOCLOUD-NETWORK HaloCloud Network Limited | Valid | - | 2026-10-26 |
| 2a14:7581:8800::/41 | AS50385 HALOCLOUD-NETWORK HaloCloud Network Limited | Valid | - | 2026-10-26 |
| 2a14:7581:8880::/41 | AS50385 HALOCLOUD-NETWORK HaloCloud Network Limited | Valid | - | 2026-10-26 |
| 2a14:7581:8900::/41 | AS50385 HALOCLOUD-NETWORK HaloCloud Network Limited | Valid | - | 2026-10-26 |
RPKI ROAs
| Prefix | Origin | Max Length | Trust Anchor |
|---|---|---|---|
| 2a14:7581:8000::/36 | AS50385 | /41 | ripe |
More Specific Prefixes
| Prefix | AS | Country | Status |
|---|---|---|---|
| 2a14:7581:8000::/39 | 🇯🇵JP | assigned | |
| 2a14:7581:8200::/39 | AS50385 | 🇭🇰HK | assigned |
| 2a14:7581:8400::/39 | AS50385 | 🇭🇰HK | assigned |
| 2a14:7581:8600::/39 | AS50385 | 🇸🇬SG | assigned |
Related Prefixes
Geolocation
Country🇯🇵JapanJP
CityTokyo
Abuse Contact
Learn more
- RPKI and ROAs explainedWhat RPKI valid, invalid and no ROA mean
- RPKI validatorCheck ROA coverage for any prefix or ASN
- What is BGP?How prefixes are announced and routed
- More-specific prefixesGlossary: covering and more-specific routes
- IPv4 transfer marketTransfers published by all five RIRs
API
Open https://api.ipctl.io/v1/prefix/2a14:7581:8000::/36Returns prefix allocation, BGP routes, and more-specific subnets.
curl -s "https://api.ipctl.io/v1/prefix/2a14:7581:8000::/36" | jq
External Links