Claranet operate in seven seperate countries/regions:

• The United Kingdom
• France
• Germany
• Benelux (Belgium, Netherlands, Luxemborg)
• Spain
• Portugal

We present a consistent routing policy and prefix view in every country as represented by our
AS-SET object AS-CLARANET in the RIPEDB and RADB

Our customer base consists of both private and corporate customers. Our products include dial, leased line and DSL access ,transit, customer server hosting in both our own data centres and carrier-neutral co-location facilities as well as shared web hosting, mail and high end fully managed hosting and MPLS/VPN based services. For more information about what we do, please visit us at http://www.clara.net

Claranet operate a selective peering policy which is generally open, peers must demonstrate,observe and note the following:

Technical Requirements

• For public IPv4 peerings, peers should exchange at least 50mbit/second(public) or 150mbit/second(private) of aggregate traffic with the Claranet international network measured using "95th Percentile" in either direction continually.
• No traffic restrictions exist for public IPv6 peerings, private IPv6 peerings will normally only be configured with existing IPv4 peers but this will be assessed on a case-by-case basis.
• Peers may only send unicast IPv4 or IPv6 traffic to the Claranet network for destinations where routing reachability has been announced via a mutual BGPv4 session.
• Peers may only, via a mutual BGPv4 session, announce routing reachability for prefixes for which peers have registered as originating from or transiting through peers' network infrastructure as documented in the RADB
• Claranet do not require use of an MD5 key for protecting BGPv4 sessions.
• Claranet do not support 32 bit AS Numbers (ASN32 - RFC 4893), Claranet are not currently able to configure sessions with peers who have a 32 bit AS number.

Administrative Requirements

• At present Claranet require peers to match its geographic footprint where possible.
• Peers must not have been a customer of Claranet or any of its subsidiaries for the past six months preceeding the application.If a customer relationship begins during a peering relationship the peering relationship must terminate.
• Peers may not be IPv4 reachable to Claranet via an existing peer of Claranet at any time.
• Peers must operate a 24x7 English speaking Network Operations Centre and must provide details to Claranet upon application. Claranet require operational requests are responded to and resolved in a timely fashion.
• Claranet do not require formal Settlement Free Interconnect (SFI) documentation to be completed.

Meeting the criteria specified here does not guarantee that Claranet will establish a peering relationship with the applicant.

Prospective applicants should send a mail to peering@clara.net if they wish to apply, we strongly advise that all sensitive data (such as keys) be encrypted with this PGP/GPG key

For more information about peering with Claranet, you can view our PeeringDB record