AS42695 CLEURA Cleura AB
🇸🇪Org handle: ORG-CNHA1-RIPE
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
55total
44 IPv411 IPv6
IPv4 Addresses
Allocated (RIR)34,048
Announced (BGP)40,448
IPv6 Addresses
Allocated (RIR)2×10³⁰
Announced (BGP)2×10³⁰
Prefix Limit (IPv4)
100
Prefix Limit (IPv6)
50
Country
🇸🇪 SERIR
RIPE NCCStatus
allocated
Allocated
2007-04-03
Routing hygiene
Score 7/100 · Low riskRPKI ROA coverage
94.5%
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
7
diversity 43/100
- No significant routing hygiene issues found
Based on 55 announced prefixes, updated daily (2026-10-24). How the score works · RPKI explained
Announced Prefixes
(BGP)55|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - |
1-10 of 55
1 / 6
Allocated Prefixes
(RIR)41Prefix | Country | RIR | Status |
|---|---|---|---|
| 31.12.84.0/22 | 🇸🇪 SE | RIPENCC | allocated |
| 31.132.56.0/22 | 🇸🇪 SE | RIPENCC | allocated |
| 37.153.138.0/23 | 🇸🇪 SE | RIPENCC | allocated |
| 37.153.172.0/23 | 🇸🇪 SE | RIPENCC | allocated |
| 45.114.120.0/22 | 🇸🇪 SE | RIPENCC | allocated |
| 46.254.8.0/21 | 🇸🇪 SE | RIPENCC | allocated |
| 77.81.6.0/23 | 🇸🇪 SE | RIPENCC | allocated |
| 77.81.188.0/23 | 🇸🇪 SE | RIPENCC | allocated |
| 86.107.48.0/23 | 🇸🇪 SE | RIPENCC | allocated |
| 86.107.242.0/23 | 🇸🇪 SE | RIPENCC | allocated |
1-10 of 41
1 / 5
All 55 announced prefixes of AS42695 →
Upstream Providers(4)
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS52011 | 🇸🇪Cleura-MiddleEast Cleura AB |
BGP Neighbours
(seen in AS paths)Upstreams (7)
Networks AS42695 hands its own prefixes to: transit providers, or peers at an exchange.
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/42695Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/42695" | jq