Peering Policy

Stacklayer Communications Ltd operates AS218805. This policy explains how other networks can ask to peer with us and what we expect from the networks we peer with.

Our approach

We are willing to peer with networks that meet the requirements below, at internet exchanges where we are both present, where it makes technical sense and benefits both sides. We decide each request on its merits, and we may decline or end a peering where the requirements are not met.

Where we peer

Our current peering locations, with our addresses and port sizes, are listed on the Network page. We may add, move or remove locations over time.

Who can peer with us

To peer with us you should:

• operate your own autonomous system with a valid ASN
• be present at an internet exchange where we are also present
• have a working technical or NOC contact that we can reach, and an up-to-date PeeringDB record
• carry IPv4, IPv6 or both, and be able to run BGP sessions over them
• publish accurate route objects and RPKI ROAs for the prefixes you announce

Technical requirements

• Peering is by BGP-4, with sessions across the exchange's peering LAN.
• You may announce only your own prefixes and those of your customers. Do not announce prefixes you are not authorised to announce, and do not use private ASNs or bogon address space.
• Do not point a default route or a static route at us.
• Set a sensible maximum prefix limit on your side, and keep your announcements within the limit shown in your PeeringDB record.
• We filter the routes we receive to protect our network. We may reject routes that are invalid or that we cannot verify, and we may apply prefix limits.
• Follow the rules of the exchange that we peer on.

How traffic may be used

Peering carries traffic between our customers and yours. You must not use our network for transit to other networks, and you must not send us traffic for destinations you do not have a route for. You must not resell or hand on our peering to a third party.

Operations and security

Keep your contact details in PeeringDB current and tell us before planned maintenance that will drop the session, where you can. Tell us promptly if you find a security problem or a route leak that affects us. Reports of abuse involving our network should follow our Abuse Policy.

Cost

Unless we agree otherwise in writing, peering is settlement-free. Each network pays for its own equipment, ports and exchange membership.

How to ask for peering

Submit a support ticket in our client area marked as a peering request, and include:

• your ASN and a link to your PeeringDB record
• the exchange and the addresses you want to peer on
• the address families you want to use, IPv4, IPv6 or both
• a technical contact for your network

We will reply when we have looked at it. We do not promise a fixed response time.

Changes and ending a peering

We review this policy from time to time. We may suspend or remove a session if you break this policy, our Acceptable Use Policy or the exchange's rules, if the session threatens the security or stability of our network, or if it is no longer of benefit to both sides. We will give notice where we reasonably can, but we may act immediately where there is a risk to the network.

You may end a peering at any time. Tell us first if you can.