AS8239 NEXTLEVEL-CONNECTIVITY-ISP LYNTIA NETWORKS S.A.
🇪🇸Org handle: ORG-DDCS1-RIPE
Servicios Masivos ISP (Grupo Lyntia Networks)
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)8,192
Announced (BGP)8,192
IPv6 Addresses
Allocated (RIR)1.9×10²⁵
Announced (BGP)1.9×10²⁵
Routing hygiene
Score 18/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
50%
1 prefix registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
- 50% of announced prefixes (1 of 2) have no IRR route object for this ASN
Based on 2 announced prefixes, updated daily (2026-10-23). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | - | |
| Valid | - | - |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 212.59.192.0/19 | 🇪🇸 ES | RIPENCC | allocated |
| 2001:ac0:c800::/44 | 🇪🇸 ES | RIPE | assigned |
All 2 announced prefixes of AS8239 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS8239 hands its own prefixes to: transit providers, or peers at an exchange.
- AS8903AS8903 LYNTIA NETWORKS S.A2
Transfer History
Registry transfers of AS8239 between organisations.
- AS8239M&A ·
- AS8239M&A ·
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/8239Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/8239" | jq