2a12:3fc6::/44 - GiraffeTech Sichuan Giraffe Technology (AS57330)
CIDR
2a12:3fc6::/44
IP Version
IPv6
Addresses
19.3Y
Mask
/44
Country
🇲🇾 Malaysia
City
Kuala Lumpur
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 |
|---|---|---|---|---|
| 2a12:3fc6::/48 | AS57330 GiraffeTech Sichuan Giraffe Technology Co., Ltd. | Valid | - | 2026-10-11 |
| 2a12:3fc6:1::/48 | AS57330 GiraffeTech Sichuan Giraffe Technology Co., Ltd. | Valid | - | 2026-10-11 |
| 2a12:3fc6:2::/48 | AS57330 GiraffeTech Sichuan Giraffe Technology Co., Ltd. | Valid | - | 2026-10-11 |
| 2a12:3fc6:3::/48 | AS57330 GiraffeTech Sichuan Giraffe Technology Co., Ltd. | Valid | - | 2026-10-11 |
RPKI ROAs
| Prefix | Origin | Max Length | Trust Anchor |
|---|---|---|---|
| 2a12:3fc6::/44 | AS57330 | /48 | ripe |
IRR Route Objects
| Origin | Registry | Maintainer | Modified |
|---|---|---|---|
| AS57330 | RIPE | GIRAFFE-MNT | 2026-09-10 |
More Specific Prefixes
| Prefix | AS | Country | Status |
|---|---|---|---|
| 2a12:3fc6::/48 | AS57330 | 🇨🇳CN | assigned |
| 2a12:3fc6:1::/48 | AS57330 | 🇭🇰HK | assigned |
| 2a12:3fc6:2::/48 | AS57330 | 🇯🇵JP | assigned |
| 2a12:3fc6:3::/48 | AS57330 | 🇩🇪DE | assigned |
| 2a12:3fc6:e::/48 | 🇭🇰HK | assigned | |
| 2a12:3fc6:f::/48 | 🇨🇳CN | assigned |
Transfer History
Registry transfers of 2a12:3fc6::/44, blocks inside it, or blocks containing it.
- 2a12:3fc0::/29Transfer ·
| Date | Resource | From | To | Type |
|---|---|---|---|---|
| 2a12:3fc0::/29 | DAOport Internet Infrastructure Holdings Limited | TwentyWAN MB | Transfer |
Related Prefixes
More prefixes of AS57330
All prefixes of AS57330 →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/2a12:3fc6::/44Returns prefix allocation, BGP routes, and more-specific subnets.
curl -s "https://api.ipctl.io/v1/prefix/2a12:3fc6::/44" | jq
External Links