Peering policy

We are a small network and peer openly where it shortens a path. The requirements below are the ones we actually check; there is no traffic ratio requirement and no minimum volume.

Requirements

A registered ASN and up-to-date contact records.
Route objects for every prefix you announce to us, in a database we can query.
RPKI ROAs for those prefixes. We drop invalids and do not make exceptions.
A 24/7 reachable NOC address. A personal mailbox is not sufficient.
No default route, no pointing static routes at us.

Technical expectations

Item	Expectation
Session type	eBGP, multihop only where the fabric requires it
Max prefix	Set on both sides, agreed before the session comes up
Prefix length accepted	/24 and shorter for IPv4, /48 and shorter for IPv6
MD5 / TCP-AO	Available on request, not required
Communities	We honour standard no-export and blackhole communities
Blackhole	/32 and /128 accepted from direct peers, next-hop discard
MTU	1500 on public fabrics; jumbo on private interconnect by agreement
Graceful shutdown	Supported, please use it for maintenance

Presence

Location	Fabric	Capacity	State
Moscow	public fabric	2 × 10G	active
Moscow	private interconnect	10G	active
Amsterdam	public fabric	10G	active
Frankfurt	public fabric	10G	provisioning

What we will not do

We do not sign non-disclosure agreements to exchange routes, we do not pay for settlement-free peering, and we do not de-peer to create leverage in a commercial negotiation. If a session is not useful to both sides we say so and take it down with notice.

Requesting a session

Mail peering@clouderra.ru with your ASN, the fabrics where you are present, the prefix counts you expect to announce and your max-prefix preference. We reply within five business days, including when the answer is no.

Depeering and maintenance notices go to the address on file, not to this page. Keep your contact record current.