Skip to main content
my.TurkIX Apply Now
Locations
Home Connection Policy

Connection Policy

Network Standards

What we ask of every connecting network

Clear technical and operational rules help every member exchange traffic securely, predictably and at scale.

These requirements are designed to protect the shared exchange fabric, improve routing hygiene, and ensure stable peering sessions for all participants.

Apply Now Contact Us
10 core requirements
7 prohibited protocol groups
PeeringDB profile required
Member must:

Mandatory member requirements

Every connected member is expected to maintain accurate routing data, use approved addressing on the peering LAN, and keep the interconnection clean and secure.

  • Have registered AS number (autonomous system) and at least one IP prefix.
  • Maintain a complete and current https://peeringdb.com profile.
  • Use on the connection interface only those IP addresses and network masks which were provided by TurkIX, and only those MAC addresses which were reported to TurkIX.
  • Announce BGP prefixes in accordance with routing policy in RIPE, ARIN or RADB databases. In addition, maintain complete and current AS-SET objects. In addition, maintain complete and current ROA objects for the RPKI protocol.
  • Only announce prefixes with its own next-hop IP address.
  • Forward traffic only to BGP prefixes received from the connection interface to TurkIX. Do not use a static route on the connection to TurkIX, or otherwise send traffic to TurkIX through any route not received via BGP.
  • Not redistribute Peering LAN networks of the traffic exchange point (194.42.47.0/26, 2001:7f8:161::/64) beyond the member's router.
  • Transmit only Ethernet frames of types: 0x0800 - IPv4, 0x0806 - ARP, 0x86dd - IPv6, 0x8100 - IEEE 802.1q.
  • Address Ethernet frames only to MAC addresses received on the connection interface to TurkIX, or to the broadcast address of ARP packets, or to the multicast address of the ICMPv6 Neighbor Discovery protocol.
  • On the interfaces connecting to TurkIX, disable all link-local protocols, Proxy ARP, IP directed broadcast, and IP redirects.
Technical facts

What you need before you apply

The values a peering engineer needs to prepare a session, in one place. Everything here also appears on the pages it belongs to.

Exchange ASN AS211877
Peering LAN (IPv4) 194.42.47.0/26
Peering LAN (IPv6) 2001:7f8:161::/64
Route servers rs1.turkix.com.tr — 194.42.47.1 · 2001:7f8:161::1
rs2.turkix.com.tr — 194.42.47.2 · 2001:7f8:161::2
Port speeds 10GE-LR4 · 40GE-LR4 · 100GE-LR4
Accepted ethertypes 0x0800 IPv4 · 0x0806 ARP · 0x86dd IPv6 · 0x8100 802.1q
Looking Glass https://lg.turkix.bg
Operational baseline

Ready to connect?

If your network meets the technical requirements, you can submit your request or contact the TurkIX team for the next step.

How to connect Contact Us
Company

Fixnet Telekom Ltd. Sti.
test

NOC & Sales

24/7 NOC — noc@turkix.com.tr
Sales — info@turkix.com.tr
05400822222
Contact →

PoPs

test
PoPs →