Skip to main content

AS34683

AS-TELKEATELECOM

TELKEA TELECOM SA

Registry

Authoritative registration data

AS number
34683
Name
AS-TELKEATELECOM
Organisation
TELKEA TELECOM SA
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS34683
212.24.192.0/19 IPv4 /19 not checked
87.254.96.0/19 IPv4 /19 not checked
185.69.216.0/22 IPv4 /22 not checked
195.137.228.0/23 IPv4 /23 not checked
2001:1698::/32 IPv6 /32 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS34683
Address families
LU-CIX 1,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS34683 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS34683 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 295 970
v4
AS6661 EPT-LU 141 243
v4 v6

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS34683 in AS paths

Observed downstreams
Families
AS210145 bourselux 48 117
v4
AS21433 AccentureFSSC 61 80
v4
AS204803 SOCGEN-LU 50 62
v4

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 8
v4
AS25091 IP-Max 1 4
v4
AS34019 HIVANE 1 4
v4

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.