AS218969 SHEEPMC-NETWORKS ZHICHENG YANG
ππ°Org handle: ORG-ZY21-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
0 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)3.1Γ10Β²βΆ
Announced (BGP)3.6Γ10Β²β΄
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
10
Country
ππ° HKRIR
RIPE NCCStatus
allocated
Allocated
2026-08-13
Routing hygiene
Score 10/100 Β· Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
Based on 1 announced prefix, updated daily (2026-10-26). How the score works Β· RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a10:fa81:1300::/40 | π―π΅ JP | RIPE | assigned |
| 2a14:7583:efea::/48 | ππ° HK | RIPE | assigned |
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 AS218969 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/218969Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/218969" | jq