Skip to main content

AS34565

TURKIX

TurkIX Communications Ltd.

Registry

Authoritative registration data

AS number
34565
Name
TURKIX
Organisation
TurkIX Communications Ltd.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

0

Total announced

0

Announced prefixes

No announced prefixes observed

Route collectors saw no announcements from this AS, or the routing data source was unavailable.

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS34565
Address families
1-BG FREE 100,000 Mbps IPv4 · IPv6
1-IX EU 100,000 Mbps IPv4 · IPv6
B-IX 100,000 Mbps IPv4 · IPv6
GNM-IX 100,000 Mbps IPv4 · IPv6
SOX Serbia 100,000 Mbps IPv4 · IPv6
TurkIX Sofia 300,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 AS34565 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS34565 in AS paths

Observed upstreams
Families
AS50629 LWLCOM 109 647
v4
AS49434 10 47
v4
AS15958 10 34
v4
AS62000 3 20
v4
AS6204 1 17
v4
AS44901 5 5
v4
AS30886 1 3
v6

No rows match “”.

Showing of

Observed downstreams

15 networks seen after AS34565 in AS paths

Observed downstreams
Families
AS44901 277 2,374
v4
AS47288 12 164
v4
AS216265 29 160
v4
AS206119 32 116
v4
AS209451 22 80
v4
AS206375 1 34
v4
AS48011 4 29
v4
AS206163 9 15
v4
AS7768 1 10
v4
AS216096 SECUREPEAK 4 9
v4 v6
AS213640 2 6
v4
AS4849 2 5
v4
AS13335 CLOUDFLARENET 3 3
v4
AS63293 1 1
v4
AS139341 ACE-AS-AP 1 1
v4

No rows match “”.

Showing of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS13004 255 2,207
v4
AS209823 6 27
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.