Link11 GmbH Peering-Policy

We are currently employing an open peering-policy.

We are free to peer with any organisation who is interested in peering with us.

Public peering

We are currently present and available for public peering at a number of internet exchangepoints.
Exchangepoints are probably the best place to exchange traffic with us. If the estimated amount of exchanged traffic exceeds a significant value, we are happy to establish Private-Peerings.

Name	Location	Connection	IPs
AMS-IX	Amsterdam, NL	10Gbit/s	195.69.145.111/22 2001:7f8:1::a503:4309:1/64
DE-CIX 1	Frankfurt, DE	40Gbit/s	80.81.192.218/22 2001:7f8::8605:0:1/64
DE-CIX 2	Frankfurt, DE	20Gbit/s	80.81.193.218/22 2001:7f8::8605:0:2/64
LINX	London, UK	10Gbit/s	195.66.224.107/23 2001:7f8:4::8605:1/64
NL-IX	Amsterdam, NL	1Gbit/s	193.239.116.9/23 2001:7f8:13::a503:4309:1/64

ID	Name	Address	Location
FFM1	InterXion	Hanauer Landstraße 304a	60314 Frankfurt, DE
FFM3	Interoute	Weißmüllerstraße 26 & 28	60314 Frankfurt, DE
FFM4	Aixit HG-Computerservice	Börsenplatz 3	60313 Frankfurt, DE
FFM5	Interwerk	Dieselstraße 37-41	60314 Frankfurt, DE
AMS1	Globalswitch	Johan Huizingalaan 759	1066 VH Amsterdam, NL
AMS2	Equinix	Luttenbergweg 4	1101 EC Amsterdam, NL
LON1	Telehouse	Coriander Avenue 14	London E14 2AA, UK

Common requirements/answers

We don't have any requirements on public peering but we want to strongly urge our peers to do complete BGP route filtering or at least have sensible max-prefixes settings on their customer bgp sessions to avoid any accidental route leaks.
We are filtering any routes larger than /24 (IPv4) and larger than /64 (IPv6).
We keep tight max-prefixes settings on our BGP peering sessions that are automatically adjusted up- and downwards based on a rolling average of the past 60 days. If you expect a sudden increase by more than 25%, please notify us in advance. If you don't notify us, the session(s) will go down once but then come up again with an adjusted max-prefixes setting on our side.
Please, if you are keeping tight max-prefixes settings as well and are not automatically adjusting the limits, have an active NOC address that can react quickly to increase requests or at least notice constantly flapping sessions and act on it. (we've recently crossed announcing 100 prefixes and tripped max-prefixes limits on 29 peerings and at the time of this writing, 56 days later, 16 of those are still down/flapping)

Last update: Tue Nov 8 14:42:42 CET 2011