AS214560 HYDRASHIELD Maxime Lescure trading as Hydra-Shield
🇫🇷Org handle: ORG-MLTA5-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
1 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)2.4×10²⁴
Announced (BGP)2.4×10²⁴
Routing hygiene
Score 16/100 · Low riskRPKI ROA coverage
66.7%
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
- 33% of announced prefixes (1 of 3) have no valid ROA
Based on 3 announced prefixes, updated daily (2026-10-22). How the score works · RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | Other IRRRIPE | 2026-10-26 | |
| No ROA | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 2.26.145.0/24 | 🇪🇺 EU | RIPE | assigned |
| 2a0f:85c1:831::/48 | 🇫🇷 FR | RIPE | assigned |
| 2a10:4646:123::/48 | 🇫🇷 FR | RIPE | assigned |
All 3 announced prefixes of AS214560 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS214560 hands its own prefixes to: transit providers, or peers at an exchange.
- AS50124EASIO COM EASIO COM SASU3
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 AS214560 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/214560Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/214560" | jq