Peering policy
Mixnet operates an open and operationally clean peering policy for networks that exchange meaningful traffic and follow current routing best practices.
- 01
General requirements
Networks wishing to peer are expected to operate a public ASN, keep their PeeringDB details up to date, provide reachable NOC contacts and keep their IRR/RPKI records current.
- 02
Routing
Mixnet expects prefix filtering, max-prefix limits, stable BGP sessions, valid route object records, and that no default, private or unauthorised transit routes are announced.
- 03
Operations
Peer networks are expected to respond to operational issues within a reasonable time, coordinate necessary maintenance windows and avoid traffic engineering that creates persistent imbalance or capacity pressure.
- 04
Interconnection
Public exchange peering is preferred where both parties have a presence. Private interconnection may be considered where traffic volume, redundancy or operational requirements justify it.
- 05
Contact
For peering requests, write to peering@mixnet.com.tr; for operational matters, write to noc@mixnet.com.tr.