AS50628 Leonix-Telecom Leonix Telecom SAS
🇫🇷Org handle: ORG-LTS34-RIPE
Leonix Telecom
RIPE NCCallocated
Announced Prefixes (BGP)
17total
11 IPv46 IPv6
IPv4 Addresses
Allocated (RIR)14,080
Announced (BGP)14,080
IPv6 Addresses
Allocated (RIR)3.1×10³⁰
Announced (BGP)3.1×10³⁰
Routing hygiene
Score 14/100 · Low riskRPKI ROA coverage
88.2%
1 prefix RPKI invalid
IRR route objects
94.1%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
4
diversity 55/100
- 12% of announced prefixes (2 of 17) have no valid ROA, 1 of them RPKI invalid
Based on 17 announced prefixes, updated daily (2026-10-21). How the score works · RPKI explained
Announced Prefixes
(BGP)17|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | - | 2026-10-26 | |
| No ROA | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 |
1-10 of 17
1 / 2
Allocated Prefixes
(RIR)16Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.144.94.0/23 | 🇫🇷 FR | RIPENCC | allocated |
| 95.214.196.0/22 | 🇫🇷 FR | RIPENCC | allocated |
| 178.208.0.0/19 | 🇫🇷 FR | RIPENCC | allocated |
| 185.173.68.0/22 | 🇫🇷 FR | RIPENCC | allocated |
| 185.173.96.0/22 | 🇫🇷 FR | RIPENCC | allocated |
| 185.194.156.0/22 | 🇫🇷 FR | RIPENCC | allocated |
| 193.35.98.0/24 | 🇫🇷 FR | RIPENCC | allocated |
| 193.35.101.0/24 | 🇫🇷 FR | RIPENCC | allocated |
| 193.35.145.0/24 | 🇫🇷 FR | RIPENCC | allocated |
| 193.35.156.0/24 | 🇫🇷 FR | RIPENCC | allocated |
1-10 of 16
1 / 2
All 17 announced prefixes of AS50628 →
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS50628 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (8)
Networks whose own prefixes AS50628 passes on: usually its customers.
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/50628Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/50628" | jq