AS206628 EzriCloud Tianyu-Zhu
🇺🇸Org handle: ORG-TA1443-RIPE
EzriCloud
RIPE NCCallocated
Announced Prefixes (BGP)
6total
2 IPv44 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)2×10²⁵
Announced (BGP)4.8×10²⁴
Routing hygiene
Score 11/100 · Low riskRPKI ROA coverage
83.3%
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
2
diversity 44/100
- 17% of announced prefixes (1 of 6) have no valid ROA
Based on 6 announced prefixes, updated daily (2026-10-21). How the score works · RPKI explained
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | ARIN | 2026-10-23 | |
| Valid | ARIN | 2026-10-23 | |
| Valid | RIPE | 2026-10-23 | |
| No ROA | ARIN | 2026-10-23 | |
| Valid | RIPE | 2026-10-23 | |
| Valid | RIPE | 2026-10-23 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 2001:678:d3c::/48 | 🇺🇸 US | RIPENCC | assigned |
| 2a0f:85c1:30::/44 | 🇬🇧 GB | RIPE | assigned |
All 6 announced prefixes of AS206628 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS206628 hands its own prefixes to: transit providers, or peers at an exchange.
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/206628Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/206628" | jq