AS34683 AS-TELKEATELECOM TELKEA TELECOM SA
π±πΊOrg handle: ORG-NIP1-RIPE
TELKEA TELECOM SA
RIPE NCCallocated
Announced Prefixes (BGP)
5total
4 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)17,920
Announced (BGP)17,920
IPv6 Addresses
Allocated (RIR)7.9Γ10Β²βΈ
Announced (BGP)7.9Γ10Β²βΈ
Prefix Limit (IPv4)
20
Prefix Limit (IPv6)
5
Country
π±πΊ LURIR
RIPE NCCStatus
allocated
Allocated
2005-03-16
Routing hygiene
Score 10/100 Β· Low riskRPKI ROA coverage
100%
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
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
Based on 5 announced prefixes, updated daily (2026-10-23). How the score works Β· RPKI explained
Announced Prefixes
(BGP)5|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-23 | |
| Valid | RIPE | 2026-10-23 | |
| Valid | RIPE | 2026-10-23 | |
| Valid | RIPE | 2026-10-23 | |
| Valid | RIPE | 2026-10-23 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 87.254.96.0/19 | π±πΊ LU | RIPENCC | allocated |
| 185.69.216.0/22 | π±πΊ LU | RIPENCC | allocated |
| 195.137.228.0/23 | π±πΊ LU | RIPENCC | assigned |
| 212.24.192.0/19 | π±πΊ LU | RIPENCC | allocated |
| 2001:1698::/32 | π±πΊ LU | RIPENCC | allocated |
All 5 announced prefixes of AS34683 β
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS201973 | π±πΊCURIA-AS European Court of Justice |
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS34683 hands its own prefixes to: transit providers, or peers at an exchange.
- AS6661EPT LU POST Luxembourg5
Downstreams (1)
Networks whose own prefixes AS34683 passes on: usually its customers.
- AS21433AccentureFSSC Accenture UK Limited1
Other adjacent networks (1)
Adjacent to AS34683 in the transit part of AS paths: peers, providers or customers.
- AS6939Hurricane Electric1
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/34683Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/34683" | jq