AS214647 YADDA Yadda OU
πͺπͺOrg handle: ORG-YO23-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
133total
130 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)3,840
Announced (BGP)33,280
IPv6 Addresses
Allocated (RIR)6.3Γ10Β²βΉ
Announced (BGP)6.3Γ10Β²βΉ
Prefix Limit (IPv4)
500
Prefix Limit (IPv6)
10
Country
πͺπͺ EERIR
RIPE NCCStatus
allocated
Allocated
2026-04-28
Routing hygiene
Score 32/100 Β· Medium riskRPKI ROA coverage
92.5%
8 prefixes RPKI invalid
IRR route objects
92.5%
8 prefixes registered for another origin
Hijack signals
6
4 announced against others' ROAs, 2 own announced by others
Upstreams
2
diversity 1/100
- Announces 4 prefixes that RPKI assigns to another network (possible hijack or misconfiguration)
- Routes concentrated on one upstream (99% of routes)
- 8% of announced prefixes (10 of 133) have no valid ROA, 8 of them RPKI invalid
Based on 133 announced prefixes, updated daily (2026-10-25). How the score works Β· RPKI explained
Announced Prefixes
(BGP)133|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Invalid | - | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - |
1-10 of 133
1 / 14
Allocated Prefixes
(RIR)16Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.10.209.0/24 | π©πͺ DE | RIPE | assigned |
| 82.21.125.0/24 | π¨π³ CN | RIPE | assigned |
| 82.27.36.0/24 | πͺπͺ EE | RIPE | assigned |
| 82.27.37.0/24 | πͺπͺ EE | RIPE | assigned |
| 82.27.65.0/24 | πͺπͺ EE | RIPE | assigned |
| 143.14.122.0/24 | πͺπͺ EE | RIPE | assigned |
| 143.14.198.0/24 | π¨π¦ CA | RIPE | assigned |
| 143.20.214.0/24 | πͺπͺ EE | RIPE | assigned |
| 143.20.229.0/24 | πͺπͺ EE | RIPE | assigned |
| 155.117.137.0/24 | π°π KH | RIPE | assigned |
1-10 of 16
1 / 2
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 AS214647 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/214647Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/214647" | jq