Link11 GmbH Peering-Policy

We are currently employing an selective peering-policy.

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	100Gbit/s	80.249.209.111 2001:7f8:1::a503:4309:1
Any2West	Los Angeles, US	10Gbit/s	206.72.211.184 2001:504:13:0:0:0:211:184
DE-CIX 1	Frankfurt, DE	100Gbit/s	80.81.192.218 2001:7f8::8605:0:1
DE-CIX 2	Frankfurt, DE	100Gbit/s	80.81.193.218 2001:7f8::8605:0:2
Digital Realty NYC	New York, US	10Gbit/s	206.126.115.237 2001:504:17:115::237
Equinix Singapore	Singapore, SG	10Gbit/s	27.111.229.156 2001:de8:4::3:4309:1
LINX	London, UK	100Gbit/s	195.66.224.107 2001:7f8:4::8605:1
SwissIX	Zürich, CH	10Gbit/s	91.206.52.175 2001:7f8:24::af

ID	Name	Address	Location
FFM7	Equinix (Ancotel)	Kleyerstraße 88	60326 Frankfurt, DE
FFM14	Interxion	Hanauer Landstrasse 298	60314 Frankfurt, DE
AMS1	Globalswitch	Johan Huizingalaan 759	1066 VH Amsterdam, NL
LON2	Telehouse North	Coriander Avenue 14	London E14 2AA, UK
LAX1	Coresite LA	624 S. Grand Ave., Ste. 110	Los Angeles CA 90017, US
MIA1	telX Miami	36 NE Second Street	Miami FL 33132, US
NYC1	telX New York	60 Hudson Street	New York NY 10013, US
ZRH1	Interxion Zuerich	Saegereistrasse 35	CH-8152 Glattbrugg Zürich, CH
SGP1	Equinix Singapore	20 Ayer Rajah Crescent	Singapore 139964 Singapore, SG

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 on peering BGP sessions 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. Update:580 days later, 5 are still flapping)

Last update: Thu Mar 31 14:15:07 CEST 2022