Peering policy

AS213513 operates an open peering policy and welcomes peering with other networks. The following guidelines are used to evaluate peering requests. They are guidelines rather than an exhaustive list, and any peering may carry additional terms by mutual agreement.

General requirements

The peer holds number resources from an appropriate RIR (RIPE, ARIN, APNIC, LACNIC or AFRINIC).
The peer maintains an accurate and current PeeringDB record.
The peer operates a 24/7 NOC reachable for operational and security matters.
The peer is not a downstream transit customer of Computle.

Routing requirements

Announce a consistent, aggregated set of prefixes at all interconnection points.
Register all announced routes in a recognised IRR (RIPE preferred); we build prefix filters from IRR data.
Publish and maintain valid RPKI ROAs. We validate and drop RPKI-invalid routes.
Minimum accepted prefix length is /24 for IPv4 and /48 for IPv6.
Do not point a default route or static routes towards AS213513.
Apply sensible max-prefix limits on both IPv4 and IPv6 sessions.

Interconnection

Public peering over the LINX route servers is our preferred method. If you are present at an exchange where we peer, you will receive our routes automatically.
Direct (bilateral) sessions are established where there are sufficient traffic levels between our networks to justify a dedicated session, or by mutual agreement.
Both IPv4 and IPv6 are supported and peers are expected to enable both where available.

Operational

Peers are expected to remain compliant with this policy for the duration of the peering. We reserve the right to suspend a session that no longer meets it.
MD5 session authentication is available on request.
The NO_EXPORT community and standard BGP communities are honoured.

How to peer

If you are present at LINX LON1, peer with our route servers — no request is required. For a direct session, email [email protected] with your AS number, company name, the exchange point(s) and your peering addresses.