Welcome to AS400442

Peering Policy for AS400442

1. Peering Criteria

• Your network must have a valid Autonomous System Number (ASN) and IP allocations from a Regional Internet Registry (RIR), Local Internet Registry (LIR), or a similar entity.
• Your network must support IPv6.
• You must operate a Network Operations Centre (NOC) reachable by email.
• You must be willing to establish a bilateral peering relationship with AS400442 and exchange traffic on a settlement-free basis.
• You must have a valid PeeringDB page.
• You must keep your Internet Routing Registry (IRR) and registry data up-to-date.

2. Peering Locations

AS400442 is happy to peer at any location that works for both parties. We are open to peering at Internet Exchange Points (IXPs).

3. Follow Our Routing Policy

When peering with AS400442, please ensure you follow these routing policies:

• See below.

4. Maintenance and Support

AS400442 operates as a hobby network with no guarantees of service availability. We maintain our network on a best-effort basis and strive to respond promptly to routing issues with existing peers. We expect the same level of courtesy in return.

AS400442 attempts to automatically update IRR-based filters at least once a day.

5. Termination

AS400442 reserves the right to terminate peering with any network that violates this peering policy or is deemed detrimental to the stability and reliability of AS400442.

6. Modification

This peering policy may be modified by AS400442 at any time. Changes will be communicated to existing and potential peers.

• Reject default routes from non-upstream peers.
• Reject AS paths using BGP AS_SET notation.
• Reject prefixes smaller than our minimum and larger than our maximum prefix lengths.
• Reject bogons (unallocated or reserved IP address ranges).
• Reject AS paths over 50 hops.
• Reject AS paths using AS0 or AS23456.
• Reject RPKI invalids.
• Do not announce any prefix that doesn’t belong to your AS or a downstream.
• Do not announce any prefix longer than a /24 (IPv4) or /48 (IPv6).
• Do not announce routes pointing to bogons or they will be filtered.
• Do not announce routes with private or invalid ASNs in the AS path.
• All announced prefixes must be valid according to IRR and/or RPKI. Invalid prefixes will be filtered.
• Announced routes should be aggregated if possible to avoid routing table inflation.
• Do not announce our prefixes to other ASes unless we have a transit agreement.
• Do not send us traffic destined for prefixes we don’t announce.