AS213891 LIUZHEN-AS Liu Zhen
π¨π³Org handle: ORG-LZ18-RIPE
Liu Zhen Network
RIPE NCCallocated
Announced Prefixes (BGP)
10total
0 IPv410 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)3.9Γ10Β²βΆ
Announced (BGP)1.2Γ10Β²β΅
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
50
Country
π¨π³ CNRIR
RIPE NCCStatus
allocated
Allocated
2024-11-08
Routing hygiene
Score 8/100 Β· Low riskRPKI ROA coverage
90%
no RPKI invalid prefixes
IRR route objects
90%
1 prefix registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
4
diversity 66/100
- 10% of announced prefixes (1 of 10) have no valid ROA
Based on 10 announced prefixes, updated daily (2026-10-24). How the score works Β· RPKI explained
Announced Prefixes
(BGP)10|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | - | 2026-10-27 | |
| Valid | - | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | - | 2026-10-27 | |
| Valid | Other IRR | 2026-10-27 | |
| No ROA | Other IRR | 2026-10-27 |
Allocated Prefixes
(RIR)9Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a0e:aa07:e150::/44 | π©πͺ DE | RIPE | assigned |
| 2a0e:aa07:e15f::/48 | π©πͺ DE | RIPE | assigned |
| 2a14:67c1:a060::/44 | π¬π§ GB | RIPE | assigned |
| 2a14:67c1:b000::/40 | π¬π§ GB | RIPE | assigned |
| 2a14:67c1:b000::/48 | π¦πΆ AQ | RIPE | assigned |
| 2a14:67c3:e620::/44 | πΈπ¬ SG | RIPE | assigned |
| 2a14:67c3:e622::/48 | πΈπ¬ SG | RIPE | assigned |
| 2a14:7580:770::/44 | πͺπΊ EU | RIPE | assigned |
| 2a14:7580:777::/48 | πΈπ¬ SG | RIPE | assigned |
All 10 announced prefixes of AS213891 β
BGP Neighbours
(seen in AS paths)Upstreams (4)
Networks AS213891 hands its own prefixes to: transit providers, or peers at an exchange.
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 AS213891 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/213891Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/213891" | jq