46,30 ₺ 11:47
AS62425 · Peering Policy

Peering Policy

IX and private peering options on the KuzeyDC backbone. Direct traffic exchange with Cloudflare, Google and Meta; DE-CIX Istanbul and GNM-IX access.

AS62425 IX + Private IPv4 / IPv6

Peering Overview

The Kuzey Datacenter network operates under an open and selective peering policy

ASN

Autonomous System

AS62425 KuzeyDC

Istanbul-based carrier-neutral backbone; BGP services for colocation, dedicated and cloud customers.

Policy

Open Peering

Open Selective

Mutual traffic exchange with content, CDN, ISP and enterprise networks; evaluated when technical requirements are met.

IX

Internet Exchange

2+ IX points

Public peering via DE-CIX Istanbul (ISTIX) and GNM-IX; private cross-connect at KuzeyDC facility.

Support

NOC

24/7 Contact

24/7 technical contact line for peering requests and BGP incidents.

Direct Peering Partners

Active direct peering relationships with major content and cloud networks

Cloudflare

Local path optimization for CDN and security traffic

Active

Google

Low latency for Google Cloud and Workspace traffic

Active

Meta

Optimized routing for Meta infrastructure

Active

IX & Private

DE-CIX Istanbul, GNM-IX and in-facility private peering

Active

IX and Interconnection Points

Internet exchange points available for public peering and the KuzeyDC meet-me room

Internet Exchange

DE-CIX Istanbul

Istanbul — Neutral IXP serving the Turkish market under the ISTIX brand. Route server and multi-POP access.

Official site
Internet Exchange

GNM-IX

Europe / Asia — Distributed carrier-neutral IX network; Remote IX peering without physical presence.

Official site
Private Peering

KuzeyDC Meet-Me

Çekmeköy, Istanbul — Direct peering via cross-connect and private VLAN at our Tier III facility.

Peering Requirements

The following information is required to evaluate your peering request

  • Valid ASN and RIPE (or relevant RIR) registration
  • Announced IPv4 and/or IPv6 prefix list (route objects / RPKI)
  • 24/7 reachable NOC or technical contact (email + phone)
  • Up-to-date AS and facility data on your PeeringDB profile
  • Commitment to filter bogons, spam and abuse traffic
  • Maximum prefix limits and MD5/TCP-AO requirements disclosed

Technical Parameters

BGP IPv4 and IPv6 dual-stack; 2-byte and 4-byte ASN support
RPKI ROV (Route Origin Validation) recommended
Communities Custom BGP community sets available on request
Max-prefix Per-session limits defined in the peering agreement
Looking Glass Route and ping tests via lg.kuzeydc.com

Peering Request Process

1. Submit Information

Share your ASN, prefix list and NOC contact via the contact form or peering email.

2. Technical Review

Our NOC evaluates routing policy, traffic profile and IX access suitability.

3. Session Setup

After approval, BGP sessions are scheduled over IX or private cross-connect.

4. Monitoring

Sessions are monitored 24/7; NOC contact remains open for prefix changes and incidents.

Tools & Resources

Knowledge Base

What is your peering policy?

KuzeyDC applies an open and selective peering policy. Mutual traffic exchange is evaluated when technical requirements and operational compatibility are met.

At which IX points can we peer?

Public peering is available via DE-CIX Istanbul and GNM-IX. Direct private peering is also offered at our Çekmeköy, Istanbul facility via cross-connect.

Is there a minimum traffic requirement?

There is no fixed minimum traffic quota; mutual benefit and technical fit are evaluated.

Is IPv6 peering supported?

Yes. IPv4 and IPv6 dual-stack BGP sessions are supported; route validation with RPKI is recommended.

How do I submit a peering request?

Use the contact form or email info@kuzeydc.com with your ASN and prefix information. Our NOC team will review the request.

Submit a Peering Request

Contact us with your ASN, prefix list and NOC details; our technical team will evaluate peering options.

AS62425