Cleura AB - AS42695 - Peering Policy

Cleura has an open peering policy.

We will peer with any network we share an IX or POP with
but we do require that if we share multiple locations, we peer
on at least one of those locations in each country.

We will however NOT initiate any new peering relationship
with a party currently announcing bogons and/or prefixes
with invalid ROA or invalid IRR records.

We will announce our RIPE DB registered as-set AS-CLEURA which
contains all our transit customers in addition to AS42695.

We will filter all traffic to illegal destinations such as
address ranges defined in RFC1918, and we will impose
prefix filters on all peering sessions.

We ask that peering partners maintain an updated as-set
record in an IRR of their choice and tell us which IRR
and which as-set. We further encourage our peers to keep
an up to date record on peeringdb.com.

We require dual-stack peering (both IPv4 and IPv6), on
separate BGPv4 sessions.

We do not allow using a peering session for transit
purposes such as setting us as default gateway.

The peering relationship will be settlement free, we will
never charge for a peering session, and we will not pay
for a peering session.

The peering will be based on good will and best-effort,
neither part is liable to the other party for any kind
of losses or damage from interruption of peering for
any period of time.

We encourage sharing operational contact details, for
example 24x7 NOC phone/email details. For private peers
this is a must.


Peering contact: peering@cleura.com

Cleura NOC: noc@cleura.com

For up to date POP and IX list, see: https://www.peeringdb.com/net/7670

For up to date routing policy, see: https://apps.db.ripe.net/db-web-ui/#/lookup?source=ripe&key=AS42695&type=aut-num