Customer Peering

Free peering for cloudKleyer customers

For our customers we offer the possibility of free peering with other cloudKleyer customers via public peering.

This eliminates the costs for crossconects between customers at different locations.

The fixed reserved bandwidth significantly reduces network costs. Participation in cloudKleyer allows to build up redundancy and increase the network quality.

Private Peering

cloudKleyer IX private peering enables direct data exchange between two participants via a dedicated VLAN over the cloudKleyer infrastructure.

The Private Peering Interconnect VLAN can be implemented either on a dedicated port or on an existing port with (802.1) Q-tagging.

  • cloudKleyer will assign a private VLAN, in the form of a VPLS instance
  • cloudKleyer configures a port in the Private Peering VLAN and assigns it to the client.
  • cloudKleyer will configure a port in the Private Peering VLAN and assign it to the subscriber.
  • cloudKleyer will not assign IP addresses in the private peering LANs. This is the responsibility of the parties involved.

Customers can connect to a private peering through a dedicated port or through an existing port with a selected 802.1Q tag. Both parties can contact cloudKleyer NOC in case of problems.

VPN/VLAN Global Connect

Implementation of a connection to cloudKleyer IX.

Interested parties can connect to cloudKleyer IX either via VLAN or via a physical connection Exchange.

cloudKleyer IX can be reached via DE-CIX

    Connection options:
  • 10 Mb/25 Mb/50 Mb/100 Mb/200 Mb/300 Mb/500 Mb/750 Mb/1 Gb/2 Gb/10 Gb
  • The connection can be provided at various locations in the metro and regional area as well as in the international area.
  • Furthermore, the equipment can be placed in one of the participating data centres.

Our peering policy allows customers to connect directly to 485 providers.

Policy & FAQ

The connection to the cloudKleyer Frankfurt IX is either via a physical connection at one of the locations or via VLAN or IP transit to the cloudKleyer IX node.

For the cloudKleyer colocation customers the organisation takes over the in-house cabling. For the other organisations the organisation of the physical or virtual connection is the responsibility of the customer. The following types are possible as cross connection interfaces:

  • 1000 Basic TX
  • 1000 Basic LX
  • 10000 Basic SR, LR, LRM, ER

Access to cloudKleyer IX can be realised if the customer has its own Autonomous System (AS). If you do not have an AS, we can offer you a solution for this case.

The Customer is obliged to keep the Routing Network Policy of his own AS up to date in the Internet Routing Registry (IRR) RIPE, ARIN or RADB.

The customer must deactivate the auto-sensing mode on all interfaces and explicitly define the configuration interface (duplex, speed, etc.).

The Customer must disable ARP proxy, broadcast forwarding, spanning tree, IP redirects, CDP and all types of layer 2 broadcast – except ARP and ICMPv6 Neighbor Discovery – on all interfaces.

The Customer is obliged to specify the MAC addresses of all logical interfaces used for the connection to GE-CIX.

The Customer is obliged to transmit Ethernet frames only on the MAC addresses at each interface used for the connection to GE-CIX and received via this interface.

The Customer is obliged to send Ethernet frames from the only logical interface for each connection used for the connection to GE-CIX.

The customer is obliged to send only Ethernet frames of the following types ( 0x0800 – IPv4, 0x0806 – ARP, 0x86dd – IPv6, as general and on the Multicast VLAN.

The Customer is obliged to use only the assigned IP address and netmask on all interfaces used to connect to cloudKleyer IX. The Customer shall not disclose the IP address of cloudKleyer IX to third parties.

The Customer is obligated to use the BGP4 protocol to establish peering sessions.

The Customer is obligated to route traffic via the cloudKleyer IX only into the networks that have been announced for the Customer via the cloudKleyer IX.

The Customer is obliged to keep the Internet routes RIPE, ARIN or objects such as RADB-Route and/or Route6 announced by the Customer in RS up to date for all its networks AS.

The Customer is obliged to announce the RS network in accordance with the description of the routing policy of these networks in the Internet routes of the register. In particular, the attributes AS_PATH announced networks last AS number must match the object’s original field of origin such as “route” and/or “route6” in the Internet routes of the Registry.

The Customer shall not notify RS private network, private AS, the default route.

The Customer undertakes to ensure the connectivity of its own network with other participants of cloudKleyer IX.

Consulting request

Contact Information


Phone:  +49 (0)69 66 169 67-80


If you send the data entered in the contact form by clicking on the following button, you declare that you have taken note of the data protection declaration and agree to the electronic collection and storage of the data provided.

The data will only be used strictly for the purpose of processing and answering your inquiry. By sending the contact form, you declare that you agree to the processing of your data. You can revoke your consent at any time with effect for the future. In the event of revocation, your data will be deleted immediately.

Please enable JavaScript in your browser to complete this form.

Fill out hte application and wait for a call from our specialists