2a0d:2580:1000::/36 - Moe Network Moe Overflow Electric Limited (AS213262)
CIDR
2a0d:2580:1000::/36
IP Version
IPv6
Addresses
4951.7Y
Mask
/36
Country
πΉπΌ Taiwan
City
Neihu District
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
4 more-specific announcements| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| 2a0d:2580:1081::/48 | AS213262 Moe-Network Moe Overflow Electric Limited | Valid | - | 2026-10-12 |
| 2a0d:2580:1344::/48 | AS213262 Moe-Network Moe Overflow Electric Limited | Valid | - | 2026-10-12 |
| 2a0d:2580:1604::/48 | AS213262 Moe-Network Moe Overflow Electric Limited | Valid | - | 2026-10-12 |
| 2a0d:2580:1702::/48 | AS213262 Moe-Network Moe Overflow Electric Limited | Valid | - | 2026-10-12 |
RPKI ROAs
| Prefix | Origin | Max Length | Trust Anchor |
|---|---|---|---|
| 2a0d:2580:1000::/36 | AS213262 | /48 | ripe |
IRR Route Objects
| Origin | Registry | Maintainer | Modified |
|---|---|---|---|
| AS213262 | RIPE | cute-mnt | 2021-06-08 |
More Specific Prefixes
| Prefix | AS | Country | Status |
|---|---|---|---|
| 2a0d:2580:1081::/48 | AS213262 | π―π΅JP | assigned |
| 2a0d:2580:1344::/48 | AS213262 | πΈπ¬SG | assigned |
| 2a0d:2580:1352::/48 | πͺπΊEU | assigned | |
| 2a0d:2580:1604::/48 | AS213262 | π¨π¦CA | assigned |
| 2a0d:2580:1702::/48 | AS213262 | πΊπΈUS | assigned |
| 2a0d:2580:1852::/48 | ππ°HK | assigned | |
| 2a0d:2580:1886::/48 | AS213262 | πΉπΌTW | assigned |
Transfer History
Registry transfers of 2a0d:2580:1000::/36, blocks inside it, or blocks containing it.
- 2a0d:2580::/29Transfer Β·
| Date | Resource | From | To | Type |
|---|---|---|---|---|
| 2a0d:2580::/29 | KV Solutions B.V. | Angelo Kreikamp trading as Forhosting | Transfer |
Related Prefixes
Geolocation
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/2a0d:2580:1000::/36Returns prefix allocation, BGP routes, and more-specific subnets.
curl -s "https://api.ipctl.io/v1/prefix/2a0d:2580:1000::/36" | jq
External Links