TURKNET PEERING POLICY
AS12735
1. Overview & Scope
This document defines TurkNet's (AS12735) policies, requirements, and procedures for
establishing BGP peering.
It applies to:
- Public peering (IXPs)
- Private peering (PNI)
- Sponsored interconnections
TurkNet follows a selective peering policy, aiming to ensure stable, secure, and scalable
interconnections aligned with industry best practices.
2. Network Overview
TurkNet operates a high-capacity national and international backbone providing reliable
connectivity to ISPs, carriers, and content providers.
Infrastructure highlights:
- 10G / 100G / 400G ports in major cities across Turkiye
- Direct peering with local ISPs and content networks
- High-capacity global IP transit connectivity
- Own fiber routes across Turkiye's border countries
Wholesale services include:
- Colocation
- Local tail access
- Internet access
- IP transit
- Point to Point Services
- Datacenter interconnect
3. Peering Policy & Eligibility
TurkNet evaluates peering requests based on:
- Mutual benefit and traffic optimization
- Traffic volume and balance
- Geographic and network presence
- Operational maturity
Minimum requirements:
- Public ASN and IRR AS-SET
-
Valid prefixes:
- IPv4: /24 minimum
- IPv6: /48 recommended
- RPKI ROAs properly configured
- Active PeeringDB record
- 24x7 NOC availability
- Dual-stack support (IPv4 & IPv6)
4. Technical & Interconnection Requirements
Routing & BGP:
- BGPv4 required (IPv4 & IPv6)
- No static routing
-
Max-prefix limits:
-
Accepted prefix lengths:
- IPv4: up to /24
- IPv6: up to /48
- BGP Communities supported
- MD5 authentication optional
- Graceful Restart recommended
Filtering & Validation:
- IRR-based filtering required
- RPKI validation enforced
- No route leaks tolerated
Interconnection options:
A minimum traffic level of 5 Gbps is required. Requests below this threshold will be evaluated
based on our peering strategy and network requirements.
-
Public peering (IXP):
- 10 Gbps standard
- 100/400 Gbps for high-volume peers
-
Private peering (PNI):
- 10 Gbps standard
- 100/400 Gbps for high-volume peers
Capacity planning:
- Upgrade required at 80% utilization
- Redundant links are recommended for traffic volumes above 40G
5. Traffic & Security Policy
Peering acceptance is based on:
- Sufficient and stable traffic volume
- Balanced traffic exchange
- Contribution to network efficiency
Security expectations:
- Support for BGP blackholing
- DDoS detection and mitigation capabilities
- Proper abuse handling processes
6. Operations & Peering Process
Operational requirements:
- 24x7 NOC support
- Planned maintenance: ≥ 1 week notice
- Emergency maintenance: immediate notification
- Continuous monitoring of sessions and traffic
Peering process:
-
Send request to peering@turk.net
Subject: Peering Request — AS<ASN> — <Location>
-
Include:
- PeeringDB link
- ASN
- IRR details
- NOC contact
- Location
- Port capacity
- Prefixes
- Traffic estimate
- TurkNet reviews and validates
- Session is configured and tested
- Peering becomes operational
7. Commercial & Exceptions
- Settlement-free peering is preferred
-
Commercial terms may apply in case of:
- Traffic asymmetry
- High-volume traffic
- Dedicated infrastructure (PNI)
Exceptions may be granted for:
- Research and education networks
- Government institutions
- Content providers and CDNs
8. Contacts & Policy Management
9. Carrier Neutral Datacenters where you can connect to TurkNet's Network
- TurkNet Datacenter / Istanbul
- Equinix IL2 / Istanbul
- MedNatilus / Istanbul
- Turk Telekom Ulus DC / Ankara
- Sofia Telepoint / Bulgaria