AS205651 CATOFES Hao Qiao
π¨π³Org handle: ORG-CL412-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)1.9Γ10Β²β΅
Announced (BGP)1.9Γ10Β²β΅
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
π¨π³ CNRIR
RIPE NCCStatus
allocated
Allocated
2017-07-03
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.234.215.0/24 | πΊπΈ US | RIPE | assigned |
| 2a0d:2904::/44 | π―π΅ JP | RIPE | assigned |
All 2 announced prefixes of AS205651 β
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS205651 hands its own prefixes to: transit providers, or peers at an exchange.
- AS23961MNI AP Misaka Network2
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 AS205651 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/205651Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/205651" | jq