AS213994 DESTAKBUBBLE DESTAKBUBBLE LDA
🇵🇹Org handle: ORG-DL594-RIPE
-----BEGIN TOKEN-----09f16273bd843fc502edf36f5cb6ce8e125d68a3f571f5e6b5115d47b69bf4716fd3ef97faa941c65faa07aba75803d7bad4115a4afb8b28f7db9e3eb4f31f89-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Routing hygiene
Score 90/100 · High riskRPKI ROA coverage
0%
1 prefix RPKI invalid
IRR route objects
0%
1 prefix registered for another origin
Hijack signals
1
1 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- 100% of announced prefixes (1 of 1) have no valid ROA, 1 of them RPKI invalid
- Announces 1 prefix that RPKI assigns to another network (possible hijack or misconfiguration)
- 100% of announced prefixes (1 of 1) have no IRR route object for this ASN
- Only one upstream seen in the AS paths of its routes
Based on 1 announced prefix, updated daily (2026-10-12). How the score works · RPKI explained
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Invalid | - | 2026-10-12 |
All 1 announced prefix of AS213994 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS213994 hands its own prefixes to: transit providers, or peers at an exchange.
- AS16276OVH SAS1
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 AS213994 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/213994Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/213994" | jq