• Looking Glass
• Peering Policy
• BGP Communities
• Home

Peering Policy

This peering policy describes the criteria that M247 Ltd has chosen for acting in peering relationships. This peering policy consists in establishing peering connections between M247 Ltd and peering networks where such exchanges are mutually equitable and cost-effective.

Please keep in mind that this policy is only a guideline.

Therefore, M247 Ltd may refuse or agree to setup peering without any justification, and might even shutdown active peering sessions provided a prior 24 hours notice is issued. M247 Ltd may also change this peering policy at any time.
Applications sent for peering should be sent no more as once per 6 months and to peering@m247.com, response can be expected within 5 workdays.

General rules

• The peering partner must have an Autonomous System Number assigned by one of the five Regional Internet Registries, and use the BGP4 protocol for peering sessions.
• The peering partner must NOT abuse the peering relationship by doing any of the following: point default route, reset next hop, sell or give the next hop to third parties, and so forth unless granted by M247 Ltd.
• The peering partner must maintain a 24/7 Network Operations Centre.
• The peering partner must announce the same set of routes at all peering points, both for IPv4 and IPv6 sessions.
• The peering partner must peer in at least 2 European countries.
• The peering partner may implement filtering (AS, routes, prefix-limit) but must inform M247 Ltd about its setup, and whenever any changes occur.
• The peering partner must NOT announce prefixes longer than /24.
• The peering partner shall keep its Peering DB objects up to date.
• The exchanged traffic must never exceed in a permanent basis the 75% of the physical interconnection capacity.
• The peering partner must read and accept this agreement.

Public peering policy

This policy is valid for both IPv4 and IPv6 address families.

M247 Ltd will announce all its routes : own network and all customers. M247 Ltd doesn't require the peering partner to maintain an inbound:outbound ratio, but a certain traffic level has to be matched in order to accept the peering. Peering both in IPv4 and IPv6 is highly preferred.

Public national peering locations

M247 Ltd requires peering partners only peering inside the United Kingdom territory to peer at least in two of the following Internet Exchange Points:

• LINX Juniper LAN - London, UK
• LINX Extreme LAN - London, UK
• IXManchester - Manchester, UK
• Edge-IX - Manchester, UK

Public international peering locations

M247 Ltd requires international peering partners to peer in at least two European Internet Exchange Points from the list below:

• LINX - London, UK or IXManchester - Manchester, UK
• AMS-IX - Amsterdam, NL
• DE-CIX - Frankfurt, DE

Traffic levels for public peering

The aggregated traffic volume must be at least equal to 100 Mbit/s, if the requesting part is not already seen via a previously established peering agreement by M247 Ltd. If this condition applies the minimum aggregated traffic volume must be at least equal to 250 Mbit/s.

Private peering policy

M247 Ltd can interconnect privately at the following locations:

• M247 Ltd Datacentre (building 1 and 2), Manchester, UK
• Telecity Kilburn/Williams House, Manchester, UK
• Telecity Reynolds House, Manchester, UK
• Telecity Sinergy House, Manchester, UK
• Telehouse Docklands, London, UK
• Telecity Meridian Gate, London, UK
• Telecity Harbour Exchange, London, UK
• Telecity Sovereign House, London, UK
• Telecity 2, Amsterdam, NL
• Nikhef, Amsterdam, NL
• AXS Datahouse, Bruxelles, BE
• Telehouse Voltaire, Paris, FR
• Ancotel, Frankfurt, DE
• Sitel, Prague, CZ

Traffic levels for private peering

The aggregated traffic volume must be at least equal to 1 Gbit/s and to 500 Mbit/s at each interconnection. M247 Ltd also requires, when possible, the requesting part to support both IPv4 and IPv6 peering.